GNOME Bugzilla – Bug 577532
libsoup fails to work under proxy server
Last modified: 2009-08-12 12:36:42 UTC
Please describe the problem: libsoup does not work under proxy server . it tries to resolve the address by itself instead of letting the proxy resolve the address . Steps to reproduce: 1.run the test program get with proxy option -p 2.it fails instantly citing the error unable to resolve hostname Actual results: syed@localhost:~/libsoup$./get -p http://user:pass@proxy:port/ http://www.google.com/ /index.html: 2 Cannot resolve hostname Expected results: Does this happen every time? yes Other information: oh and i am using xfce not gnome would this make any difference ?
see http://mail.gnome.org/archives/libsoup-list/2009-April/msg00008.html
see also RFC1919 section 3.2.3 : ( http://tools.ietf.org/html/rfc1919#page-14 ) 3.2.3 DNS requirements In most classical-proxy configurations, client systems pass the desired server name (or address) to the proxy system WITHOUT INTERPRETING IT. Because of this, the client system DOES NOT REQUIRE to be able to resolve the name of the server system in order to access it through a classical proxy. It only needs to be able to resolve the name of the proxy (if referencing the proxy system by name). ... (see RFC)
For SSL see http://tools.ietf.org/html/rfc2817#page-5
I encountered this problem using webkit/libsoup on an embedded device (no gnome) behind a proxy. From what I can tell from the git logs nothing has been added yet (with 2.26.2 due < May 18th I think?). I am interested in seeing a resolution to this bug. Does anyone know if it will be included with the 2.26.2 release or perhaps in a future release? Thanks, David
I second David. I encountered the same issue in the same circumstances. Definitely very interested in a quick resolution and a potential fix date. Thank you, Christophe
(In reply to comment #5) > I second David. I encountered the same issue in the same circumstances. > Definitely very interested in a quick resolution and a potential fix date. > Thank you, > Christophe > As a dirty `fix', we could provide a valid /etc/resolve.conf on the device, thus resolve won't fail and connection through proxy can work as expected. This works at least for me.
(In reply to comment #6) > (In reply to comment #5) > > I second David. I encountered the same issue in the same circumstances. > > Definitely very interested in a quick resolution and a potential fix date. > > Thank you, > > Christophe > > > > As a dirty `fix', we could provide a valid /etc/resolve.conf on the device, > thus resolve won't fail and connection through proxy can work as expected. This > works at least for me. > I think this works only if you have a valid DNS server inside your network, which at least I do not.
To corroborate the previous comment, the dirty fix does not work for some network configurations. Would it be possible to get a feel on when an expected fix date or release would be? (as we need to take action soon) Thank you
fixed in master. will eventually go into the gnome-2-26 branch for GNOME 2.26.3, to be released July 1.
Great, thanks a lot Dan. Just to let you know that your fix is verified in our environment.
*** Bug 579434 has been marked as a duplicate of this bug. ***