<feed xmlns='http://www.w3.org/2005/Atom'>
<title>curl/tests/data/test175, branch master</title>
<subtitle>cURL mirror with patches applied
</subtitle>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/'/>
<entry>
<title>Do not mix CRLF and LF header endings in a couple of HTTP tests</title>
<updated>2012-11-19T09:58:02+00:00</updated>
<author>
<name>Fabian Keil</name>
<email>fk@fabiankeil.de</email>
</author>
<published>2012-11-14T18:49:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=ab0fa55780b518502ff0712f37e8352323389cde'/>
<id>ab0fa55780b518502ff0712f37e8352323389cde</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Added some &lt;keywords&gt; sections and use some key words more consistently.</title>
<updated>2007-10-12T01:44:22+00:00</updated>
<author>
<name>Dan Fandrich</name>
<email>dan@coneharvesters.com</email>
</author>
<published>2007-10-12T01:44:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=d7fbe07ee24f2bf1e0f158577a7c995426ef9958'/>
<id>d7fbe07ee24f2bf1e0f158577a7c995426ef9958</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Replaced 127.0.0.1 with %HOSTIP where possible</title>
<updated>2007-09-14T19:32:31+00:00</updated>
<author>
<name>Dan Fandrich</name>
<email>dan@coneharvesters.com</email>
</author>
<published>2007-09-14T19:32:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=05e4a3026da7c2dfbd3ed340a01d4a221a721168'/>
<id>05e4a3026da7c2dfbd3ed340a01d4a221a721168</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Updated the test harness to add a new "crypto" feature check and updated the</title>
<updated>2007-03-09T23:39:42+00:00</updated>
<author>
<name>Dan Fandrich</name>
<email>dan@coneharvesters.com</email>
</author>
<published>2007-03-09T23:39:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=e12d46ac50ddce4330d1a2e1d4a7e5e2accd280e'/>
<id>e12d46ac50ddce4330d1a2e1d4a7e5e2accd280e</id>
<content type='text'>
appropriate test case to use it.  For now, this is treated the same as the
"SSL" feature because curl doesn't list it separately.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
appropriate test case to use it.  For now, this is treated the same as the
"SSL" feature because curl doesn't list it separately.
</pre>
</div>
</content>
</entry>
<entry>
<title>Convert (most of) the test data files into genuine XML.  A handful still</title>
<updated>2007-01-23T02:25:56+00:00</updated>
<author>
<name>Dan Fandrich</name>
<email>dan@coneharvesters.com</email>
</author>
<published>2007-01-23T02:25:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=33bea767ebd0bbf11867fe1af31dc345e9f816af'/>
<id>33bea767ebd0bbf11867fe1af31dc345e9f816af</id>
<content type='text'>
are not, due mainly to the lack of support for XML character entities
(e.g. &amp; =&gt; &amp;amp; ).  This will make it easier to validate test files using
tools like xmllint, as well as edit and view them using XML tools.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
are not, due mainly to the lack of support for XML character entities
(e.g. &amp; =&gt; &amp;amp; ).  This will make it easier to validate test files using
tools like xmllint, as well as edit and view them using XML tools.
</pre>
</div>
</content>
</entry>
<entry>
<title>Venkat Akella found out that libcurl did not like HTTP responses that simply</title>
<updated>2006-11-25T13:32:04+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2006-11-25T13:32:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=da58d03ff7be9fc5e0219d95ce2f9932e2272473'/>
<id>da58d03ff7be9fc5e0219d95ce2f9932e2272473</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Modified the default HTTP headers used by libcurl:</title>
<updated>2005-05-11T09:52:59+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2005-05-11T09:52:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=5d9fc28fa760e1b0b7f68fce7ae845f4e659e0fd'/>
<id>5d9fc28fa760e1b0b7f68fce7ae845f4e659e0fd</id>
<content type='text'>
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"
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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"
</pre>
</div>
</content>
</entry>
<entry>
<title>A minor "syntax error" in numerous test files corrected</title>
<updated>2005-01-25T21:45:03+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2005-01-25T21:45:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=f2e71edcbd479345678bb03e76fad17157fc318e'/>
<id>f2e71edcbd479345678bb03e76fad17157fc318e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>HTTP "auth done right". See lib/README.httpauth</title>
<updated>2004-11-24T16:11:35+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2004-11-24T16:11:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=3e1caa61859a6057a65eb7c1585d47e05026c4f2'/>
<id>3e1caa61859a6057a65eb7c1585d47e05026c4f2</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Now the test servers and test cases can run on a custom port number. There's</title>
<updated>2004-09-08T08:08:38+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2004-09-08T08:08:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=2b1673c9c83f693fdf243607f9141e5e897e0ba8'/>
<id>2b1673c9c83f693fdf243607f9141e5e897e0ba8</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
</feed>
