Feature Requests item #2827023, was opened at 2009-07-25 16:14
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=2827023&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: libcurl
Group: None
Status: Open
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Olaf van der Spek (olafvdspek)
Assigned to: Daniel Stenberg (bagder)
Summary: More specific 'couldn't connect' error

Initial Comment:
"Couldn't connect to server" isn't very specific. Could it be replaced by at least 'refused' and 'timed out'?

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2009-07-25 23:33

Message:
Ok, moving this to the Feature Requests. My advice on how to proceed still
stands though.

----------------------------------------------------------------------

Comment By: Olaf van der Spek (olafvdspek)
Date: 2009-07-25 20:17

Message:
> Sorry, but this is not a bug but a request for a modified
behavior/description.

Oops. Could you move this issue to the feature requests tracker?

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2009-07-25 19:41

Message:
Sorry, but this is not a bug but a request for a modified
behavior/description.

But yes, a more descriptive error text would be very easy and even a new
return code to clarify the error(s) could be a good idea. For the latter,
I'd suggest you take the issue to the curl-library list for discussion. For
the first case, you can proceed and submit a patch to the same list.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=2827023&group_id=976
Received on 2009-07-25