In the cURL documentation, there is an option called CURLOPT_HTTPPROXYTUNNEL
which is defined to create a tunnel via the proxy when enabled.
However, I have no idea what the tunnel is and what does it do. What difference will it make if I don't use a tunnel like this?
curl_setopt($session, CURLOPT_HTTPPROXYTUNNEL, 1)
UPDATE:
What I got is that the tunnel is referring to an HTTP CONNECT METHOD
and here is what I understand it does:
An HTTP-based tunneling method uses the HTTP CONNECT method/command. A client issues the HTTP CONNECT command to an HTTP proxy. The proxy then makes a TCP connection to a particular server:port, and relays data between that server:port and the client connection. Because this creates a security hole, CONNECT-capable HTTP proxies commonly restrict access to the CONNECT method. The proxy allows access only to a whitelist of specific authorized servers.
So, the question is, what is the difference between connecting to a proxy with and without CONNECT method?
Without CURLOPT_HTTPPROXYTUNNEL
Without CURLOPT_HTTPPROXYTUNNEL
: You just use the proxy address/port as a destination of your HTTP request. The proxy will read the HTTP headers of your query, forward your request to the destination (with your HTTP headers) and then write the response to you.
Example steps :
HTTP GET /index.html
sent to 1.1.1.1 (proxy)
1.1.1.1
receive request and parse header for getting the final destination of your HTTP request.1.1.1.1
forward your query and headers to www.site.com (destination in request headers)
.1.1.1.1
write back to you the response receive from www.site.com
With CURLOPT_HTTPPROXYTUNNEL
With CURLOPT_HTTPPROXYTUNNEL
: You ask the proxy to open a direct binary connection (like HTTPS, called a TCP Tunnel
) directly to your destination by doing a CONNECT
HTTP request. When the tunnel is ok, the proxy write you back a HTTP/1.1 200 Connection established
. When it received your browser start to query the destination directly : The proxy does not parse HTTP headers and theoretically does not read tunnel datas, it just forward it, thats why it is called a tunnel !
Example steps :
HTTP CONNECT
sent to 1.1.1.1
1.1.1.1
receive HTTP CONNECT
and get the ip/port of your final destination (header
field of HTTP CONNECT
).1.1.1.1
open a TCP Socket
by doing a TCP handshake
to your destination 2.22.63.73:80 (ip/port of www.site.com)
. 1.1.1.1
Make a tunnel by piping your TCP Socket
to the TCP Socket
opened to 2.22.63.73:80
and then write you back HTTP/1.1 200 Connection established
witch means that your client can now make your query throw the TCP Tunnel
(TCP datas received will be transmited directly to server and vice versa).