cURL
Haxx ad
libcurl

curl's project page on SourceForge.net

Sponsors:
Haxx

cURL > Mailing List > Monthly Index > Single Mail

curl-tracker Archives

[curl:bugs] #1281 libcurl shows proxy port instead of destination port on SSL failure

From: Daniel Stenberg <bagder_at_users.sf.net>
Date: Thu, 26 Sep 2013 20:46:14 +0000

The error message problem is now fixed. Closing this report.

---
** [bugs:#1281] libcurl shows proxy port instead of destination port on SSL failure**
**Status:** closed-fixed
**Labels:** proxy 
**Created:** Wed Sep 18, 2013 03:04 PM UTC by Gordon Marler
**Last Updated:** Sat Sep 21, 2013 07:46 PM UTC
**Owner:** Daniel Stenberg
When using curl command line to upload a file to an HTTPS destination via a proxy, the port for the proxy is substituted in place of the ultimate destination's port, causing failure.
This appears to be a problem from at least curl v7.21.2 to the present version.  It happen whether you use the -x <proxyhost>:<port> option or HTTPS_PROXY/ALL_PROXY.
Here's a (sanitized) example:
 # export HTTPS_PROXY=myproxy.example.com:82
 # curl -v -T vmdump.3 'https://supportfiles.sun.com:443/cURL?file=vmdump-nydevsol10-20130917-IDR615.7&root=cores'
* About to connect() to proxy myproxy.example.com port 82 (#0)
*   Trying 192.168.77.59...
* Failed to set TCP_KEEPALIVE on fd 6
* Adding handle: conn: 0x6d2c0
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x6d2c0) send_pipe: 1, recv_pipe: 0
* Connected to myproxy.example.com (192.168.77.59) port 82 (#0)
* Establish HTTP proxy tunnel to supportfiles.sun.com:443
> CONNECT supportfiles.sun.com:443 HTTP/1.1
> Host: supportfiles.sun.com:443
> User-Agent: curl/7.32.0
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 Connection established
< 
* Proxy replied OK to CONNECT request
* SSLv3, TLS handshake, Client hello (1):
* Unknown SSL protocol error in connection to supportfiles.sun.com:82 
* Closing connection 0
curl: (35) Unknown SSL protocol error in connection to supportfiles.sun.com:82 
Note how curl shows supportfiles.sun.com:443 first, then later changes it to supportfiles.sun.com:82 later on, at which point the SSL handshake failure occurs.
Obviously, have confirmed that the proxy works as expected with other browsers and command line tools without issue.  Only curl seems to have this problem.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
Received on 2013-09-26

These mail archives are generated by hypermail.

donate! Page updated May 06, 2013.
web site info

File upload with ASP.NET