Venkat Akella found out that libcurl did not like HTTP responses that simply
[platform/upstream/curl.git] / tests / data / test264
1 <info>
2 <keywords>
3 HTTP
4 HTTP GET
5 HTTP proxy
6 HTTP proxy Basic auth
7 </keywords>
8 </info>
9 # Server-side
10 <reply>
11 <data>
12 HTTP/1.1 200 OK swsclose\r
13 Date: Thu, 09 Nov 2010 14:49:00 GMT\r
14 Content-Type: text/html\r
15 Content-Length: 26\r
16 \r
17 the content would go here
18 </data>
19 </reply>
20
21 # Client-side
22 <client>
23 <server>
24 http
25 </server>
26  <name>
27 HTTP with proxy string including http:// and user+password
28  </name>
29  <command>
30 http://we.want.that.site.com/264 -x http://f%61ke:user@%HOSTIP:%HTTPPORT
31 </command>
32 </client>
33
34 # Verify data after the test has been "shot"
35 <verify>
36 <strip>
37 ^User-Agent:.*
38 </strip>
39 <protocol>
40 GET http://we.want.that.site.com/264 HTTP/1.1\r
41 Proxy-Authorization: Basic ZmFrZTp1c2Vy\r
42 Host: we.want.that.site.com\r
43 Pragma: no-cache\r
44 Accept: */*\r
45 Proxy-Connection: Keep-Alive\r
46 \r
47 </protocol>
48 </verify>