<feed xmlns='http://www.w3.org/2005/Atom'>
<title>curl/tests/data/test560, branch gemini-meta</title>
<subtitle>cURL mirror with patches applied
</subtitle>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/'/>
<entry>
<title>testsuite: changed HTTP and RTSP header line-endings to CRLF</title>
<updated>2014-02-14T19:12:26+00:00</updated>
<author>
<name>Marc Hoersken</name>
<email>info@marc-hoersken.de</email>
</author>
<published>2014-01-31T23:52:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=69745aaa45634308c1dca29cbb7881001c6efc5d'/>
<id>69745aaa45634308c1dca29cbb7881001c6efc5d</id>
<content type='text'>
According to RFC 2616 and RFC 2326 individual protocol elements, like
headers and except the actual content, are terminated by using CRLF.

Therefore the test data files for these protocols need to contain
mixed line-endings if the actual protocol elements use CRLF while
the file uses LF.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
According to RFC 2616 and RFC 2326 individual protocol elements, like
headers and except the actual content, are terminated by using CRLF.

Therefore the test data files for these protocols need to contain
mixed line-endings if the actual protocol elements use CRLF while
the file uses LF.
</pre>
</div>
</content>
</entry>
<entry>
<title>Added test case 560:</title>
<updated>2008-11-11T21:59:25+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2008-11-11T21:59:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=d07d1a6ef85d6e42d3e376935cdede698c968556'/>
<id>d07d1a6ef85d6e42d3e376935cdede698c968556</id>
<content type='text'>
This test was added after the HTTPS-using-multi-interface with OpenSSL
regression of 7.19.1 to hopefully prevent this embarassing mistake from
appearing again... Unfortunately the bug wasn't triggered by this test, which
presumably is because the connect to a local server is too fast/different
compared to the real/distant servers we saw the bug happen with.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This test was added after the HTTPS-using-multi-interface with OpenSSL
regression of 7.19.1 to hopefully prevent this embarassing mistake from
appearing again... Unfortunately the bug wasn't triggered by this test, which
presumably is because the connect to a local server is too fast/different
compared to the real/distant servers we saw the bug happen with.
</pre>
</div>
</content>
</entry>
</feed>
