Proxy requests socket's closure. WinSSL writes to it anyway? #1239
Curl must be compiled with WinSSL support. I'm using Curl 7.52.1 and Windows 8.1.
My VC12 build configuration is:
We don't have access to the proxy server where this issue was originally observed.
Therefore to reproduce this problem we require a proxy server which always responds with a 407 (proxy authentication required) and asks for the connection to be closed.
I achieved this with the following NodeJS script:
Curl command line
Once the dummy proxy is running, we can enter the following curl command:
The correct error message for curl to give in this scenario is:
The text was updated successfully, but these errors were encountered:
This bug can probably be fixed with a single if-statement. With my very limited knowledge of the code I'd tentatively suggest this if-statement. Works for me in the two simple test cases I've tried.
@Antony74 thank you for the bug report and the dummy proxy code!
I think the bug should be solved like this (I've used the same comment as in