curl/tests/data/test174, branch master cURL mirror with patches applied Add keywords for a couple of currently keyword-less HTTP tests 2012-11-19T09:58:14+00:00 Fabian Keil fk@fabiankeil.de 2012-11-13T13:02:42+00:00 81d96c4421450a04e1fa4ba6e606ed569781065c 






Do not mix CRLF and LF header endings in a couple of HTTP tests
2012-11-19T09:58:02+00:00

Fabian Keil
fk@fabiankeil.de

2012-11-14T18:49:12+00:00

ab0fa55780b518502ff0712f37e8352323389cde

Consistently use CRLF instead. The mixed endings weren't
documented so I assume they were unintentional.

This change doesn't matter for curl itself but makes using
the tests with a proxy between curl and the test server
more convenient.

Tests that consistently use no carriage returns were
left unmodified as one can easily work around this.





Consistently use CRLF instead. The mixed endings weren't
documented so I assume they were unintentional.

This change doesn't matter for curl itself but makes using
the tests with a proxy between curl and the test server
more convenient.

Tests that consistently use no carriage returns were
left unmodified as one can easily work around this.







Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14T19:32:31+00:00

Dan Fandrich
dan@coneharvesters.com

2007-09-14T19:32:31+00:00

05e4a3026da7c2dfbd3ed340a01d4a221a721168












Convert (most of) the test data files into genuine XML.  A handful still
2007-01-23T02:25:56+00:00

Dan Fandrich
dan@coneharvesters.com

2007-01-23T02:25:56+00:00

33bea767ebd0bbf11867fe1af31dc345e9f816af

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.





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.







Venkat Akella found out that libcurl did not like HTTP responses that simply
2006-11-25T13:32:04+00:00

Daniel Stenberg
daniel@haxx.se

2006-11-25T13:32:04+00:00

da58d03ff7be9fc5e0219d95ce2f9932e2272473

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.





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.







Modified the default HTTP headers used by libcurl:
2005-05-11T09:52:59+00:00

Daniel Stenberg
daniel@haxx.se

2005-05-11T09:52:59+00:00

5d9fc28fa760e1b0b7f68fce7ae845f4e659e0fd

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"





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"







A minor "syntax error" in numerous test files corrected
2005-01-25T21:45:03+00:00

Daniel Stenberg
daniel@haxx.se

2005-01-25T21:45:03+00:00

f2e71edcbd479345678bb03e76fad17157fc318e












HTTP "auth done right". See lib/README.httpauth
2004-11-24T16:11:35+00:00

Daniel Stenberg
daniel@haxx.se

2004-11-24T16:11:35+00:00

3e1caa61859a6057a65eb7c1585d47e05026c4f2












Now the test servers and test cases can run on a custom port number. There's
2004-09-08T08:08:38+00:00

Daniel Stenberg
daniel@haxx.se

2004-09-08T08:08:38+00:00

2b1673c9c83f693fdf243607f9141e5e897e0ba8

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.





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.







added test 174, HTTP POST --anyauth to server without auth requirements.
2004-06-14T09:16:39+00:00

Daniel Stenberg
daniel@haxx.se

2004-06-14T09:16:39+00:00

2ed0728cef3e8ab6e448e902cbb8aac621aafc4b

An attempt to repeat a reported auth problem. Works for me!





An attempt to repeat a reported auth problem. Works for me!