<feed xmlns='http://www.w3.org/2005/Atom'>
<title>curl/tests/data/test516, 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>testsuite: use binary output mode for custom curl test tools</title>
<updated>2014-02-14T19:12:27+00:00</updated>
<author>
<name>Marc Hoersken</name>
<email>info@marc-hoersken.de</email>
</author>
<published>2014-01-31T23:58:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=75f00de55c6e8adc513f9ee32383b11e23106a40'/>
<id>75f00de55c6e8adc513f9ee32383b11e23106a40</id>
<content type='text'>
Do not try to convert line-endings to CRLF on Windows by setting stdout
to binary mode, just like the curl tool does if --ascii is not specified.

This should prevent corrupted stdout line-ending output like CRCRLF.

In order to make the previously naive text-aware tests work with
binary mode on Windows, text-mode is disabled for them if it is not
actually part of the test case and line-endings are corrected.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Do not try to convert line-endings to CRLF on Windows by setting stdout
to binary mode, just like the curl tool does if --ascii is not specified.

This should prevent corrupted stdout line-ending output like CRCRLF.

In order to make the previously naive text-aware tests work with
binary mode on Windows, text-mode is disabled for them if it is not
actually part of the test case and line-endings are corrected.
</pre>
</div>
</content>
</entry>
<entry>
<title>tests: add keywords for a couple of HTTP tests</title>
<updated>2013-08-11T17:56:05+00:00</updated>
<author>
<name>Fabian Keil</name>
<email>fk@fabiankeil.de</email>
</author>
<published>2012-11-19T16:54:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=001758760b162e9facdaceea30e05789989f5a31'/>
<id>001758760b162e9facdaceea30e05789989f5a31</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</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>Andres Garcia's text mode fix for the 'data' part</title>
<updated>2005-06-03T14:06:03+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2005-06-03T14:06:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=29aafb9cea842321e7379685e33194a1b34bb0dc'/>
<id>29aafb9cea842321e7379685e33194a1b34bb0dc</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</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>Fix behaviour when passing NULL to CURLOPT_POSTFIELDS and CURLOPT_HTTPPOST.</title>
<updated>2004-11-11T23:11:04+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2004-11-11T23:11:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=59c063dfd38972e06a7f3a0b8f94860a67acdc96'/>
<id>59c063dfd38972e06a7f3a0b8f94860a67acdc96</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
