Skip to content

http: fix CONNECT_ONLY with Negotiate authentication#655

Closed
MarcelRaad wants to merge 1 commit intocurl:masterfrom
MarcelRaad:connect_only_negotiate
Closed

http: fix CONNECT_ONLY with Negotiate authentication#655
MarcelRaad wants to merge 1 commit intocurl:masterfrom
MarcelRaad:connect_only_negotiate

Conversation

@MarcelRaad
Copy link
Member

Since 79b9d5f, connections were closed immediately before the libcurl user had a chance to extract the socket if Negotiate authentication was used. If CURLOPT_CONNECT_ONLY is set, it is the user's responsibility to decide when to close the connection.

This pull request is the same as #520, but without the HTTP status code check.

CONNECT_ONLY connections were closed immediately before the user had a chance
to extract the socket when the proxy required Negotiate authentication.
@iboukris
Copy link
Contributor

As mention over #520 this look OK to me.

@sithglan
Copy link
Contributor

I hit this regression as well. Please apply.

@bagder bagder closed this in c2b3f26 Apr 26, 2016
@bagder
Copy link
Member

bagder commented Apr 26, 2016

Thanks everyone for your help and contributions!

@MarcelRaad MarcelRaad deleted the connect_only_negotiate branch April 27, 2016 02:09
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants