moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-18 07:25:14 -05:00
Code Issues Releases Wiki Activity
89ab5f4380
curl/tests/data/test95

71 lines
1.3 KiB
Plaintext
Raw Normal View History

keyword update
2005-04-27 05:59:47 -04:00
<info>
<keywords>
HTTP
HTTP POST
proxytunnel
</keywords>
</info>
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Content-Type: text/html
Funny-head: yesyes
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring.
2006-11-25 08:32:04 -05:00
Content-Length: 9
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
contents
</data>
CONNECT response headers are now passed back as "regular" headers
2004-01-27 07:54:22 -05:00
<datacheck>
stricter newline policy
2004-11-29 07:01:07 -05:00
HTTP/1.1 200 Mighty fine indeed
CONNECT response headers are now passed back as "regular" headers
2004-01-27 07:54:22 -05:00
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Content-Type: text/html
Funny-head: yesyes
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring.
2006-11-25 08:32:04 -05:00
Content-Length: 9
CONNECT response headers are now passed back as "regular" headers
2004-01-27 07:54:22 -05:00
contents
</datacheck>
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
</reply>
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP over proxytunnel using POST
</name>
<command>
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://%HOSTIP:%HTTPPORT/we/want/that/page/95 -p -x %HOSTIP:%HTTPPORT -d "datatopost=ohthatsfunyesyes"
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
</command>
A minor "syntax error" in numerous test files corrected
2005-01-25 16:45:03 -05:00
</client>
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol nonewline=yes>
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
CONNECT 127.0.0.1:%HTTPPORT HTTP/1.0
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
User-Agent: curl/7.10.7-pre2 (i686-pc-linux-gnu) libcurl/7.10.7-pre2 OpenSSL/0.9.7a zlib/1.1.3
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
Host: 127.0.0.1:%HTTPPORT
Proxy-Connection: Keep-Alive
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
POST /we/want/that/page/95 HTTP/1.1
User-Agent: curl/7.10.7-pre2 (i686-pc-linux-gnu) libcurl/7.10.7-pre2 OpenSSL/0.9.7a zlib/1.1.3
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
Host: 127.0.0.1:%HTTPPORT
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 07:46:41 -05:00
Accept: */*
test 95 added, verifies my fix for bug report #848371
2003-11-25 04:06:33 -05:00
Content-Length: 27
Content-Type: application/x-www-form-urlencoded
datatopost=ohthatsfunyesyes
</protocol>
</verify>
Reference in New Issue Copy Permalink