curl/tests/data/test279, branch gemini-meta

tests: use proxy feature

2019-10-15T05:56:55+00:00

This makes the tests succeed when using --disable-proxy.

Closes https://github.com/curl/curl/pull/4488

Revert "Proxy-Connection: stop sending this header by default"

2016-08-16T06:36:04+00:00

This reverts commit 113f04e664b16b944e64498a73a4dab990fe9a68.

Proxy-Connection: stop sending this header by default

2016-02-08T10:09:40+00:00

RFC 7230 says we should stop. Firefox already stopped.

Bug: https://github.com/curl/curl/issues/633
Reported-By: Brad Fitzpatrick

Closes #633

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

- I removed the default use of "Pragma: no-cache" from libcurl when a proxy is

2008-11-19T22:00:14+00:00

  used. It has been used since forever but it was never a good idea to use
  unless explicitly asked for.

User names embedded in proxy URLs without a password were parsed

2008-08-01T02:09:08+00:00

incorrectly--the host name is treated as part of the user name and the
port number becomes the password.  This can be observed in test 279
(was KNOWN_ISSUE #54).

stricter newline policy

2007-03-03T05:16:57+00:00

stricter newline policy

2007-03-03T02:06:44+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.

Venkat Akella found out that libcurl did not like HTTP responses that simply

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

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.