GNOME Bugzilla – Bug 117496
Better handling of error 502
Last modified: 2011-12-03 17:45:24 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
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.
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.
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.
*** Bug 400017 has been marked as a duplicate of this bug. ***
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/