<testcase> <info> <keywords> HTTP SOCKS5 all_proxy </keywords> </info> # # Server-side <reply> <data> HTTP/1.1 200 OK Date: Tue, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT ETag: "21025-dc7-39462498" Accept-Ranges: bytes Content-Length: 6 Connection: close Content-Type: text/html Funny-head: yesyes -foo- </data> # method 2 is SOCKS5 asking for user+password <servercmd> method 2 user uz3r password p4ssworm backendport %HTTPPORT </servercmd> </reply> # # Client-side <client> <server> socks5 http </server> <name> SOCKS5 proxy auth </name> # target a port that won't work without the SOCKS magic <command> http://%HOSTIP:1/%TESTNUMBER -x socks5://uz3r:p4ssworm@%HOSTIP:%SOCKSPORT </command> <features> proxy </features> </client> # # Verify data after the test has been "shot" <verify> <protocol> GET /%TESTNUMBER HTTP/1.1 Host: %HOSTIP:1 User-Agent: curl/%VERSION Accept: */* </protocol> </verify> </testcase>