mirror of
https://github.com/curl/curl.git
synced 2026-08-26 19:53:31 +03:00
Known bug #47, which confused libcurl if doing NTLM auth over a proxy with
a response that was larger than 16KB is now improved slightly so that now the restriction at 16KB is for the headers only and it should be a rare situation where the response-headers exceed 16KB. Thus, I consider #47 fixed and the header limitation is now known as known bug #48.
This commit is contained in:
parent
43a4604639
commit
08fd1829e0
4 changed files with 15 additions and 5 deletions
|
|
@ -3,9 +3,10 @@ join in and help us correct one or more of these! Also be sure to check the
|
|||
changelog of the current development status, as one or more of these problems
|
||||
may have been fixed since this was written!
|
||||
|
||||
47. If a CONNECT response is larger than BUFSIZE when the connection is meant
|
||||
to be kept alive, the function will return prematurely and will confuse the
|
||||
rest of the HTTP protocol code.
|
||||
48. If a CONNECT response-headers are larger than BUFSIZE (16KB) when the
|
||||
connection is meant to be kept alive (like for NTLM proxy auth), the
|
||||
function will return prematurely and will confuse the rest of the HTTP
|
||||
protocol code. This should be very rare.
|
||||
|
||||
45. libcurl built to support ipv6 uses getaddrinfo() to resolve host names.
|
||||
getaddrinfo() sorts the response list which effectively kills how libcurl
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue