curl/tests/data/test522, branch master

http: always send Host: header as first header

2015-03-12T11:15:24+00:00

...after the method line:

 "Since the Host field-value is critical information for handling a
 request, a user agent SHOULD generate Host as the first header field
 following the request-line." / RFC 7230 section 5.4

Additionally, this will also make libcurl ignore multiple specified
custom Host: headers and only use the first one. Test 1121 has been
updated accordingly

Bug: http://curl.haxx.se/bug/view.cgi?id=1491
Reported-by: Rainer Canavan

testsuite: use binary output mode for custom curl test tools

2014-02-14T19:12:27+00:00

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.

testsuite: changed HTTP and RTSP header line-endings to CRLF

2014-02-14T19:12:26+00:00

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.

Always use nocheck="yes" for consistency

2009-01-07T21:57:26+00:00

Replaced 127.0.0.1 with %HOSTIP where possible

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

Convert (most of) the test data files into genuine XML. A handful still

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

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.

Andres Garcia's text mode fix for the 'data' part

2005-06-03T14:06:03+00:00

Modified the default HTTP headers used by libcurl:

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

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"

Olivier reported that even though he used CURLOPT_PORT, libcurl clearly still

2005-04-18T19:41:04+00:00

used the default port. He was right. I fixed the problem and added the test
cases 521, 522 and 523 to verify the fix.