Searched refs:CONNECT (Results 1 – 25 of 235) sorted by relevance
12345678910
6 HTTP CONNECT26 # Content-Length and Transfer-Encoding in a successful CONNECT 2xx reply.58 HTTP over proxy-tunnel ignore TE and CL in CONNECT 2xx responses72 CONNECT test.1287:%HTTPPORT HTTP/1.186 * Ignoring Content-Length in CONNECT 200 response87 * Ignoring Transfer-Encoding in CONNECT 200 response
5 HTTP CONNECT35 HTTP CONNECT with proxytunnel to unsupported FTP URL45 # The server doesn't implement CONNECT for ftp, so this must be a failure test50 CONNECT test-number:1059 HTTP/1.1
6 HTTP CONNECT22 # This is the CONNECT response53 HTTP POST using CONNECT with --proxy-ntlm but no auth is required63 CONNECT test.a.galaxy.far.far.away.1097:%HTTPPORT HTTP/1.1
6 HTTP CONNECT35 HTTPS GET with failed proxy auth (CONNECT 1.0)49 CONNECT test.anything.really.com:94 HTTP/1.0
6 HTTP CONNECT33 CONNECT to peer that returns nothing47 CONNECT %HOSTIP.1297:%HTTPPORT HTTP/1.1
5 HTTP CONNECT28 HTTP proxy CONNECT with custom User-Agent header41 CONNECT test.remote.example.com.287:%HTTPPORT HTTP/1.1
6 HTTP CONNECT42 Suppress proxy CONNECT response headers56 CONNECT %HOSTIP.1288:%HTTPPORT HTTP/1.194 CONNECT CODE: 200
6 HTTP CONNECT32 HTTP proxy CONNECT to proxy returning 40545 CONNECT test.remote.example.com.217:%HTTPPORT HTTP/1.1
5 HTTP CONNECT54 HTTP CONNECT to IPv6 numerical address66 CONNECT [1234:1234:1234::4ce]:%HTTPPORT HTTP/1.1
6 HTTP CONNECT79 HTTP proxy CONNECT auth Digest89 CONNECT test.remote.haxx.se.206:8990 HTTP/1.194 CONNECT test.remote.haxx.se.206:8990 HTTP/1.1
6 HTTP CONNECT51 HTTP CONNECT with 204 response65 CONNECT test.1904:%HTTPPORT HTTP/1.1
6 HTTP CONNECT100 HTTP proxy CONNECT with any proxyauth and proxy offers NTLM and close119 CONNECT test.remote.example.com.1021:%HTTPPORT HTTP/1.1124 CONNECT test.remote.example.com.1021:%HTTPPORT HTTP/1.1130 CONNECT test.remote.example.com.1021:%HTTPPORT HTTP/1.1
6 HTTP CONNECT53 HTTP 1.0 CONNECT with proxytunnel and proxy+host Basic authentication67 CONNECT test.80:%HTTPPORT HTTP/1.0
6 HTTP CONNECT54 HTTP CONNECT with proxytunnel getting two URLs from the same host68 CONNECT remotesite.com.275:%HTTPPORT HTTP/1.1
7 HTTP CONNECT43 HTTP 1.0 CONNECT with proxytunnel and downgrade GET to HTTP/1.057 CONNECT %HOSTIP.1078:%HTTPPORT HTTP/1.0
6 HTTP CONNECT86 HTTP proxy CONNECT auth NTLM105 CONNECT test.remote.example.com.209:%HTTPPORT HTTP/1.1111 CONNECT test.remote.example.com.209:%HTTPPORT HTTP/1.1
6 HTTP CONNECT95 HTTP proxy CONNECT auth NTLM with chunked-encoded 407 response114 CONNECT test.remote.example.com.1008:%HTTPPORT HTTP/1.1120 CONNECT test.remote.example.com.1008:%HTTPPORT HTTP/1.1
6 HTTP CONNECT86 HTTP 1.0 proxy CONNECT auth NTLM and then POST105 CONNECT test.remote.example.com.213:%HTTPPORT HTTP/1.0111 CONNECT test.remote.example.com.213:%HTTPPORT HTTP/1.0
6 HTTP CONNECT87 HTTP proxy CONNECT auth NTLM and then POST, response-body in the 407106 CONNECT test.remote.example.com.265:%HTTPPORT HTTP/1.1112 CONNECT test.remote.example.com.265:%HTTPPORT HTTP/1.1
66 # The second and third CONNECT will be made to the dynamic port number the FTP74 CONNECT ftp.site.thru.https.proxy:12345 HTTP/1.179 CONNECT ftp.site.thru.https.proxy:12345 HTTP/1.184 CONNECT ftp.site.thru.https.proxy:12345 HTTP/1.1
38 # Strip out the random part of the client id from the CONNECT message44 client CONNECT 18 00044d5154540402003c000c6375726c
60 # Strip out the random part of the client id from the CONNECT message66 client CONNECT 18 00044d5154540402003c000c6375726c
42 # Strip out the random part of the client id from the CONNECT message48 client CONNECT 18 00044d5154540402003c000c6375726c
3 Help: Operate through an HTTP proxy tunnel (using CONNECT)8 the proxy. The tunnel approach is made with the HTTP proxy CONNECT request and12 To suppress proxy CONNECT response headers when curl is set to output headers
2 Help: Suppress proxy CONNECT response headers6 When --proxytunnel is used and a CONNECT request is made don't output proxy