Anders Gustafsson remarked that requiring CURLOPT_HTTP_VERSION set to 1.0
when CURLOPT_HTTP200ALIASES is used to avoid the problem mentioned below is not very nice if the client wants to be able to use _either_ a HTTP 1.1 server or one within the aliases list... so starting now, libcurl will simply consider 200-alias matches the to be HTTP 1.0 compliant.
This commit is contained in:
@@ -14,6 +14,7 @@ This release includes the following changes:
|
||||
o added curl_multi_socket_action()
|
||||
o deprecated curl_multi_socket()
|
||||
o uses less memory in non-pipelined use cases
|
||||
o CURLOPT_HTTP200ALIASES matched transfers assume HTTP 1.0 compliance
|
||||
|
||||
This release includes the following bugfixes:
|
||||
|
||||
@@ -59,6 +60,7 @@ advice from friends like these:
|
||||
|
||||
Song Ma, Dan Fandrich, Yang Tse, Jay Austin, Robert Iakobashvil,
|
||||
James Housley, Daniel Black, Steve Little, Sonia Subramanian, Peter O'Gorman,
|
||||
Frank Hempel, Michael Wallner, Jeff Pohlmeyer, Tobias Rundstr<74>m
|
||||
Frank Hempel, Michael Wallner, Jeff Pohlmeyer, Tobias Rundstr<74>m,
|
||||
Anders Gustafsson
|
||||
|
||||
Thanks! (and sorry if I forgot to mention someone)
|
||||
|
||||
Reference in New Issue
Block a user