06-05-2012
I found that some proxies work different with cookies
That is why I added second check for Elite proxy servers.
... Now I found that some proxies work different with header "Cache-Control: no-cache" . That is why I added such header in second check.
Last edited by 654321; 11-15-2012 at 03:56 AM..
These 2 Users Gave Thanks to 654321 For This Post:
8 More Discussions You Might Find Interesting
1. Programming
Hello Everyone
Im planning to make a C program to check a proxy server if it is working or bot, test the proxy speed ,response time , as well as a proxy type.
i'm learning using libcurl right now to fetch http headers. do you guys have some links about how to check proxy headers?. Thank you.
... (0 Replies)
Discussion started by: magictalong
0 Replies
2. Programming
I'm trying to write a small utility for syntax checking. I've tried using Flex/Bison, but these seem too advanced for my task. A simpler tool would be appreciated. (1 Reply)
Discussion started by: Ilja
1 Replies
3. IP Networking
Hi,
I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Discussion started by: Rajesh_BK
0 Replies
4. Shell Programming and Scripting
Hi,
Not sure if this post belongs to this forum but I have been trying every so often to setup a simple http server in awk. After a couple of try and errors I finally came across this:
REMCONF - TCP/IP Internetworking With `gawk'
This tutorial is not to cut and paste without change, so here... (0 Replies)
Discussion started by: ripat
0 Replies
5. Programming
I am having problems receiving data from a remote server. It seems that I can send an HTTP request to any host such as http://www.google.com, but I can't get a reply.
I'm sending the host a HTTP 1.0 request that is formatted as such:
GET / HTTP/1.0
Host: http://www.google.com
Connection:... (0 Replies)
Discussion started by: shubham92
0 Replies
6. Shell Programming and Scripting
I'm fairly new to bash scripts, and all things unix in general. But I was in desperate need of this script, so I took matters into my own hands and built it!
The first script uses a password generator that creates 4 letter domain names and outputs only the ones that are available. Currently its... (0 Replies)
Discussion started by: Files
0 Replies
7. Web Development
I am having a hard time with this one. We have a websocket server listening on port 80 at myserver.com/wsDemo?ID=12. We need to test a client program by connecting it to this server through a proxy. I am trying nginx 1.2.7 as the proxy on port 8080, running on proxy-server. We want the client to... (1 Reply)
Discussion started by: glev2005
1 Replies
8. AIX
Hi,
I am trying to configure an HTTP_PROXY so that suma can reach out beyond our intranet and pull updates from the IBM website. Currently, our suma config is the default as it's not been used before. When I attempt to issue the following command sudo suma... (7 Replies)
Discussion started by: JAR1
7 Replies
LEARN ABOUT MOJAVE
curlopt_http_version
CURLOPT_HTTP_VERSION(3) curl_easy_setopt options CURLOPT_HTTP_VERSION(3)
NAME
CURLOPT_HTTP_VERSION - specify HTTP protocol version to use
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_HTTP_VERSION, long version);
DESCRIPTION
Pass version a long, set to one of the values described below. They ask libcurl to use the specific HTTP versions. This is not sensible to
do unless you have a good reason. You have to set this option if you want to use libcurl's HTTP/2 support.
Note that the HTTP version is just a request. libcurl will still prioritize to re-use an existing connection so it might then re-use a con-
nection using a HTTP version you haven't asked for.
CURL_HTTP_VERSION_NONE
We don't care about what version the library uses. libcurl will use whatever it thinks fit.
CURL_HTTP_VERSION_1_0
Enforce HTTP 1.0 requests.
CURL_HTTP_VERSION_1_1
Enforce HTTP 1.1 requests.
CURL_HTTP_VERSION_2_0
Attempt HTTP 2 requests. libcurl will fall back to HTTP 1.1 if HTTP 2 can't be negotiated with the server. (Added in 7.33.0)
The alias CURL_HTTP_VERSION_2 was added in 7.43.0 to better reflect the actual protocol name.
CURL_HTTP_VERSION_2TLS
Attempt HTTP 2 over TLS (HTTPS) only. libcurl will fall back to HTTP 1.1 if HTTP 2 can't be negotiated with the HTTPS server. For
clear text HTTP servers, libcurl will use 1.1. (Added in 7.47.0)
CURL_HTTP_VERSION_2_PRIOR_KNOWLEDGE
Issue non-TLS HTTP requests using HTTP/2 without HTTP/1.1 Upgrade. It requires prior knowledge that the server supports HTTP/2
straight away. HTTPS requests will still do HTTP/2 the standard way with negotiated protocol version in the TLS handshake. (Added in
7.49.0)
DEFAULT
CURL_HTTP_VERSION_NONE
PROTOCOLS
HTTP
EXAMPLE
TODO
AVAILABILITY
Along with HTTP
RETURN VALUE
Returns CURLE_OK if HTTP is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO
CURLOPT_SSLVERSION(3), CURLOPT_HTTP200ALIASES(3),
libcurl 7.54.0 May 01, 2016 CURLOPT_HTTP_VERSION(3)