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 117496 - Better handling of error 502
Better handling of error 502
Status: RESOLVED OBSOLETE
Product: Pan
Classification: Other
Component: general
pre-0.14.1 betas
Other Linux
: Normal enhancement
: 1.1
Assigned To: Charles Kerr
Pan QA Team
: 400017 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-07-15 19:12 UTC by nicolas.girard
Modified: 2011-12-03 17:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nicolas.girard 2003-07-15 19:12:06 UTC
In case of 502 error (too much downloaded), the following behaviour is to
be expected:
- Close all remaining connections to the related server
- Retry to connect and execute the pending tasks 3 of 4 hours later
Comment 1 jandrese 2003-08-15 12:38:05 UTC
The new behavior of Pan with 502 errors, shutting down _all_
connecitons, popping up a dialog box, and never retrying the
connection until you restart Pan is clearly suboptimal for this sort
of transient error.  
Comment 2 jim 2004-11-12 19:08:03 UTC
There should be the option to try much sooner than in 3 or 4 hours.  The
Octanews news service returns a 502 error if it thinks you went over your limit
of 3 connections at a time.  Even with pan set to 2 connections to the server,
Octanews still sometimes gives this error.  In such a case you would want it to
retry within minutes.
Comment 3 will 2005-05-04 18:44:27 UTC
i keep losing connections with octanews.  I am only allowed three speed
throttled connections to octanews, and i often see that i have 2,1, or 0
connections and can only get back to 3 by exiting and restarting pan.
Comment 4 Charles Kerr 2007-01-24 02:11:08 UTC
*** Bug 400017 has been marked as a duplicate of this bug. ***
Comment 5 Charles Kerr 2007-01-24 02:12:21 UTC
Although it's marked closed as a duplicate of this ticket,
Pavel has some interesting suggestions in #400017 worth
repeating here:

  some servers appear and disappear based on server (over)load and
  other mishaps. sooo it would be helpful if

  - server running but not accepting connections
  - the server is down

  if pan would automatically do at least some of the following

  - throttle number of concurrent connections to server (overriding temporarly
    /i.e. 1 hour/ the connection limit with a lower value)
  - temporarly disable the server /i.e. for 1 hour/