Bug 1066484 - wrong hostname used in (proxy) error reporting
Summary: wrong hostname used in (proxy) error reporting
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: curl
Version: 19
Hardware: All
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1042831
TreeView+ depends on / blocked
 
Reported: 2014-02-18 14:04 UTC by Aleksandar Kostadinov
Modified: 2014-03-09 04:46 UTC (History)
4 users (show)

Fixed In Version: curl-7.29.0-15.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-28 18:30:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Aleksandar Kostadinov 2014-02-18 14:04:33 UTC
Description of problem:
> $ curl -k -vvv --proxy socks5://192.168.122.1:8081 https://py.com.cn/ > /dev/null
> * About to connect() to proxy 192.168.122.1 port 8081 (#0)
> *   Trying 192.168.122.1...
> * Adding handle: conn: 0x10cbcf0
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0x10cbcf0) send_pipe: 1, recv_pipe: 0
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* > No route to host
> * Failed connect to py.com.cn:8081; No route to host
> * Closing connection 0
> curl: (7) Failed connect to py.com.cn:8081; No route to host

Notice how curl tries to connect to py.com.cn:8081 although user didn't specify that port. This is the port specified for use as a socks5 server.

Comment 1 Aleksandar Kostadinov 2014-02-18 14:12:03 UTC
btw curl from fedora 18 seems to work fine so this is a regression.

Comment 2 Kamil Dudka 2014-02-19 17:05:15 UTC
Seems to work fine with curl-7.32.0-4.fc20.x86_64.  It just prints a misleading error message.  It should write "Failed connect to 192.168.122.1:8081" instead.  The following upstream commit will fix it:

https://github.com/bagder/curl/commit/1cf71bd7

Comment 3 Fedora Update System 2014-02-25 13:17:25 UTC
curl-7.32.0-5.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/curl-7.32.0-5.fc20

Comment 4 Fedora Update System 2014-02-25 13:17:43 UTC
curl-7.29.0-14.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/curl-7.29.0-14.fc19

Comment 5 lnie 2014-02-26 07:00:09 UTC
curl-7.32.0-5.fc20 works

Comment 6 Kamil Dudka 2014-02-26 07:02:10 UTC
(In reply to lnie from comment #5)
> curl-7.32.0-5.fc20 works

Thanks for confirmation!

Comment 7 Fedora Update System 2014-02-26 14:05:51 UTC
Package curl-7.29.0-14.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing curl-7.29.0-14.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-3142/curl-7.29.0-14.fc19
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-02-28 18:30:48 UTC
curl-7.32.0-5.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-03-05 16:51:47 UTC
curl-7.29.0-15.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/curl-7.29.0-15.fc19

Comment 10 Fedora Update System 2014-03-05 16:52:12 UTC
curl-7.32.0-6.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/curl-7.32.0-6.fc20

Comment 11 Fedora Update System 2014-03-08 03:33:12 UTC
curl-7.32.0-6.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2014-03-09 04:46:02 UTC
curl-7.29.0-15.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.