curl/tests/data/test63

<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

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

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP with proxy authorization set in environment
 </name>
<setenv>
http_proxy=http://fake:user@%HOSTIP:%HTTPPORT/
</setenv>
 <command>
http://we.want.that.site.com/63
</command>
</client>

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

</protocol>
</verify>
keywords added 2005-04-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`HTTP proxy`
			`HTTP proxy Basic auth`
			`</keywords>`
			`</info>`
the proxy environment variables now may contain user name and password 2003-05-19 09:09:41 -04:00			`# Server-side`
			`<reply>`
			`<data>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`HTTP/1.1 200 OK swsclose`
the proxy environment variables now may contain user name and password 2003-05-19 09:09:41 -04:00			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Content-Type: text/html`

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

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP with proxy authorization set in environment`
			`</name>`
			`<setenv>`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 04:08:38 -04:00			`http_proxy=http://fake:user@%HOSTIP:%HTTPPORT/`
the proxy environment variables now may contain user name and password 2003-05-19 09:09:41 -04:00			`</setenv>`
			`<command>`
			`http://we.want.that.site.com/63`
			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
the proxy environment variables now may contain user name and password 2003-05-19 09:09:41 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET http://we.want.that.site.com/63 HTTP/1.1`
stricter newline policy 2004-11-29 07:01:07 -05:00			`Proxy-Authorization: Basic ZmFrZTp1c2Vy`
the proxy environment variables now may contain user name and password 2003-05-19 09:09:41 -04:00			`Host: we.want.that.site.com`
			`Pragma: no-cache`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
Modified the default HTTP headers used by libcurl: A) Normal non-proxy HTTP: - no more "Pragma: no-cache" (this only makes sense to proxies) B) Non-CONNECT HTTP request over proxy: - "Pragma: no-cache" is used (like before) - "Proxy-Connection: Keep-alive" (for older style 1.0-proxies) C) CONNECT HTTP request over proxy: - "Host: [name]:[port]" - "Proxy-Connection: Keep-alive" 2005-05-11 05:52:59 -04:00			`Proxy-Connection: Keep-Alive`
the proxy environment variables now may contain user name and password 2003-05-19 09:09:41 -04:00
			`</protocol>`
			`</verify>`