delta/curl.git - github.com: bagder/curl.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	http: don't parse body-related headers bodyless responses	Michael Kaufmann	2019-06-02	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	http: added options for allowing HTTP/0.9 responses	Daniel Stenberg	2018-12-21	1	-1/+2
\| \| \| \| \| \| \| \| \| \| \| \|	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
*	http: fix response code parser to avoid integer overflow	Daniel Stenberg	2017-07-31	1	-1/+1
\| \| \| \| \| \| \| \|	test 1429 and 1433 were updated to work with the stricter HTTP status line parser. Closes #1714 Reported-by: Brian Carpenter
*	spelling fixes	klemens	2017-03-26	1	-1/+1
\| \| \| \|	Closes #1356
*	HTTP: return larger than 3 digit response codes too	Daniel Stenberg	2014-10-27	1	-0/+69
	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