curl/tests/data/test279

<testcase>
<info>
<keywords>
HTTP
HTTP GET
HTTP proxy
HTTP proxy Basic auth
</keywords>
</info>

# Server-side
<reply>
<data>
HTTP/1.1 200 OK swsclose
Date: Thu, 09 Nov 2010 14:49:00 GMT
Content-Type: text/html
Content-Length: 27

the content would go here
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP with proxy string including http:// and user only
 </name>
 <command>
http://we.want.that.site.com/279 -x http://f%61ke@%HOSTIP:%HTTPPORT
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET http://we.want.that.site.com/279 HTTP/1.1
Proxy-Authorization: Basic ZmFrZTo=
Host: we.want.that.site.com
Accept: */*
Proxy-Connection: Keep-Alive

</protocol>
</verify>
</testcase>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-23 03:25:56 +01:00			`<testcase>`
stricter newline policy 2007-03-03 03:06:44 +01:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`HTTP proxy`
			`HTTP proxy Basic auth`
			`</keywords>`
			`</info>`
User names embedded in proxy URLs without a password were parsed incorrectly--the host name is treated as part of the user name and the port number becomes the password. This can be observed in test 279 (was KNOWN_ISSUE #54). 2008-08-01 04:09:08 +02:00
stricter newline policy 2007-03-03 03:06:44 +01:00			`# Server-side`
			`<reply>`
			`<data>`
stricter newline policy 2007-03-03 06:16:57 +01:00			`HTTP/1.1 200 OK swsclose`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Content-Type: text/html`
			`Content-Length: 27`

			`the content would go here`
stricter newline policy 2007-03-03 03:06:44 +01:00			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP with proxy string including http:// and user only`
			`</name>`
			`<command>`
User names embedded in proxy URLs without a password were parsed incorrectly--the host name is treated as part of the user name and the port number becomes the password. This can be observed in test 279 (was KNOWN_ISSUE #54). 2008-08-01 04:09:08 +02:00			`http://we.want.that.site.com/279 -x http://f%61ke@%HOSTIP:%HTTPPORT`
stricter newline policy 2007-03-03 03:06:44 +01:00			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
Armel Asselin fixed problems when you gave a proxy URL with user name and empty password or no password at all. Test case 278 and 279 were added to verify. 2006-09-20 23:49:41 +02:00			`GET http://we.want.that.site.com/279 HTTP/1.1`
User names embedded in proxy URLs without a password were parsed incorrectly--the host name is treated as part of the user name and the port number becomes the password. This can be observed in test 279 (was KNOWN_ISSUE #54). 2008-08-01 04:09:08 +02:00			`Proxy-Authorization: Basic ZmFrZTo=`
Armel Asselin fixed problems when you gave a proxy URL with user name and empty password or no password at all. Test case 278 and 279 were added to verify. 2006-09-20 23:49:41 +02:00			`Host: we.want.that.site.com`
			`Accept: /`
			`Proxy-Connection: Keep-Alive`

stricter newline policy 2007-03-03 03:06:44 +01:00			`</protocol>`
			`</verify>`
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-23 03:25:56 +01:00			`</testcase>`