6 Commits

Author	SHA1	Message	Date
Daniel Stenberg	e6b21d422e	runtests: provide curl's version string as %VERSION for tests ... ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037	2020-10-02 22:54:23 +02:00
Michael Kaufmann	2e5ceb3934	http: don't parse body-related headers bodyless responses ... Responses with status codes 1xx, 204 or 304 don't have a response body. For these, don't parse these headers: - Content-Encoding - Content-Length - Content-Range - Last-Modified - Transfer-Encoding This change ensures that HTTP/2 upgrades work even if a "Content-Length: 0" or a "Transfer-Encoding: chunked" header is present. Co-authored-by: Daniel Stenberg Closes #3702 Fixes #3968 Closes #3977	2019-06-02 22:58:04 +02:00
Daniel Stenberg	006ff62d8c	http: added options for allowing HTTP/0.9 responses ... Added CURLOPT_HTTP09_ALLOWED and --http0.9 for this purpose. For now, both the tool and library allow HTTP/0.9 by default. docs/DEPRECATE.md lays out the plan for when to reverse that default: 6 months after the 7.64.0 release. The options are added already now so that applications/scripts can start using them already now. Fixes #2873 Closes #3383	2018-12-21 10:49:30 +01:00
Daniel Stenberg	909283ae5a	http: fix response code parser to avoid integer overflow ... test 1429 and 1433 were updated to work with the stricter HTTP status line parser. Closes #1714 Reported-by: Brian Carpenter	2017-07-31 18:37:43 +02:00
klemens	f7df67cff0	spelling fixes ... Closes #1356	2017-03-26 23:56:23 +02:00
Daniel Stenberg	95765567d0	HTTP: return larger than 3 digit response codes too ... HTTP 1.1 is clearly specified to only allow three digit response codes, and libcurl used sscanf("%3d") for that purpose. This made libcurl support smaller numbers but not larger. It does now, but we will not make any specific promises nor document this further since it is going outside of what HTTP is. Bug: http://curl.haxx.se/bug/view.cgi?id=1441 Reported-by: Balaji	2014-10-27 16:28:10 +01:00