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 686603 - xmlReadFile fails when proxy enabled on Windows7
xmlReadFile fails when proxy enabled on Windows7
Status: RESOLVED INCOMPLETE
Product: libxml2
Classification: Platform
Component: general
2.7.7
Other Windows
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2012-10-22 05:19 UTC by Ebin
Modified: 2015-06-07 22:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ebin 2012-10-22 05:19:05 UTC 
Hello,

Hardware: x86
OS: Windows 7, 64 Bit

We have an application running on Window7 that uses libxml2. We have 2 kinds of network where we need to test this application
a) Network where all PC's are behind proxy server and
b) Network where proxy is disabled.

In (a), "xmlReadFile" API fails, in (b) it's works fine. We are passing  a URL [Its a remote internet url and not a local file] to "xmlReadFile".
Further debugging of "xmlReadFile" API, points out that "xmlNanoHTTPConnectAttempt" [defined in "nanohttp.c"] fails [in fact the "connect(s, addr, addrlen)" call fails].


On the contrary We have the same application running on on Linux FC16 64 bit, where both options (a) and (b) are working fine.

Could you please let's know how to solve this problem. Thanks in advance.
Comment 1 Daniel Veillard 2013-03-27 07:51:11 UTC 
I have no idea why the code on Windows would differ from the code in
Fedora Linux. The only difference might be that the code which looks
for the proxy information in http_proxy or HTTP_PROXY environment variables
finds them in Foedora but not on Windows.


Daniel
Comment 2 Alexandre Franke 2015-06-07 22:08:55 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide a simple test case to reproduce this issue.
Thanks!