After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 623274 - include proxy name in releated errors
include proxy name in releated errors
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: API
2.30.x
Other Linux
: Normal trivial
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2010-07-01 08:18 UTC by Stefan Sauer (gstreamer, gtkdoc dev)
Modified: 2010-07-30 14:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stefan Sauer (gstreamer, gtkdoc dev) 2010-07-01 08:18:35 UTC
In the gstreamer souphttp source we log errors. The messages we get from libsoup are a bit sparse in detail. See this example:
gst_soup_http_src_response_cb:<source> got response 3: Cannot resolve proxy hostname
gst_soup_http_src_parse_status:<source> error: Cannot resolve proxy hostname
gst_soup_http_src_parse_status:<source> error: libsoup status code 3


it would be nice to have the actual proxyname included in the messages. E.g. I have turn the proxy off in the gnome settings and no http_proxy env var set. Still apparently the use of a proxy is tried. This would be easier to debug, if the settings that libsoup attempts to use would be shown.

This is on gnome 2.30.
Comment 1 Dan Winship 2010-07-01 13:36:31 UTC
so is this just for debugging or do you plan to show that string to the user? currently msg->reason_phrase is always unlocalized (since normally it comes from the HTTP server, and HTTP more or less only allows those messages to be in English), but I guess we could localize the non-HTTP ones (SOUP_STATUS_IS_TRANSPORT_ERROR(msg->status_code)).
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2010-07-01 15:28:28 UTC
Yes, its just for the debugging. It like like "file not found" is most useful when it also tells what file it tried to access.
Comment 3 Dan Winship 2010-07-30 14:30:48 UTC
fixed to include the hostname for both proxy and destination host-related
errors