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 167281 - Support for http proxy autoconfiguration
Support for http proxy autoconfiguration
Status: RESOLVED WONTFIX
Product: straw
Classification: Deprecated
Component: general
0.25.1
Other Linux
: Normal normal
: 0.28
Assigned To: Maintainers of straw
Maintainers of straw
gnome[unmaintained]
: 167282 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-02-13 17:16 UTC by Hanna Wallach
Modified: 2011-01-13 12:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hanna Wallach 2005-02-13 17:16:43 UTC
Version details: 0.25.1
Distribution/Version: Debian testing/unstable

1. Set the machine's network proxy to "Automatic proxy configuration" (I use my
university's .pac file: http://www.cam.ac.uk/proxyconfig.pac) by going to the
GNOME menu and selecting Applications -> Desktop Preferences -> Network Proxy.
2. Open straw, and try to refresh feed(s).
3. Straw places the "cog" icon next to the feed(s) and waits, seemingly forever. 

If, however, the network proxy is set to "Direct internet connection" then feeds
update fine. 

See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245628
Comment 1 Hanna Wallach 2005-02-13 17:19:12 UTC
*** Bug 167282 has been marked as a duplicate of this bug. ***
Comment 2 Mike Auty 2005-07-06 13:18:49 UTC
Looking through the code I seem to have located two different bugs...

The first is that if the gnome proxy settings are set to an IP address then
LookupManager.get_instance().lookup in Config.py returns None, so that when
URLFeed.py tries to use the proxy, the IP isn't set.  However, setting the proxy
to a hostname doesn't cure all the problems.

The second problems seems to occur much later, and it appears that the
connection works and the servers return their data over http, the underyling
asyncore dispatcher doesn't seem to ever detect an end of stream and so doesn't
finish.  I've only really noticed this since I moved to python 2.4, so perhaps
there were some changes that went on.  Anyway, without the connection closing it
all just seems to hang in an inifinite poll.  I've located a python bug report
about asyncore not detected ends of connection if in poll mode, but it's a bit
old and I don't know if it's relevant.  (
http://sourceforge.net/tracker/index.php?func=detail&aid=953599&group_id=5470&atid=105470
)

If anyone can take this further it'd be great because at the moment straw simply
won't get anywhere.  Thanks,

Mike  5:)
Comment 3 Jan Alonzo 2007-05-18 03:05:01 UTC
retitled bug report
Comment 4 Akhil Laddha 2011-01-04 06:05:10 UTC
Straw development has been stalled and it has been unmaintained for a few years now. Maintainers don't have future development plan so i am closing bugs as WONTFIX. Please feel free to reopen the bugs in future if anyone takes the responsibility for active development.