| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This makes the tests succeed when using --disable-proxy.
Closes https://github.com/curl/curl/pull/4488
|
|
|
|
|
|
| |
... to make it a truly unified URL parser.
Closes #3017
|
|
|
|
| |
This reverts commit 113f04e664b16b944e64498a73a4dab990fe9a68.
|
|
|
|
|
|
|
|
|
| |
RFC 7230 says we should stop. Firefox already stopped.
Bug: https://github.com/curl/curl/issues/633
Reported-By: Brad Fitzpatrick
Closes #633
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...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
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
... since search engines find what they think is a URL in this, they
hammer www.haxx.se on this port!
|
|
|
|
| |
struct, and instead use the already stored string in the handler struct.
|
| |
|
|
|
|
|
| |
used. It has been used since forever but it was never a good idea to use
unless explicitly asked for.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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"
|
|
|