Hi everyone! We have a new questions-and-help centered forum at https://ask.fedoraproject.org/ and I invite you to try it out.
(This is based on the Discourse software, same as https://discussion.fedoraproject.org but with a different site mission.) This mailing list isn't going anywhere, but as the world marches on we need new ways to reach out and interact with people. The previous AskBot site had some strengths but overall wasn't as successful as I'd like it to be. So, we're trying something new. Take a look, tell us what you think, and, hopefully, stay around and participate.
On 05/02/2019 08:50 AM, Matthew Miller wrote:
Hi everyone! We have a new questions-and-help centered forum at https://ask.fedoraproject.org/ and I invite you to try it out.
I've been getting nothing but Error 503 Backend fetch failed and a Guru meditation from there for several days now.
On Thu, May 02, 2019 at 10:18:22AM -0600, Joe Zeff wrote:
On 05/02/2019 08:50 AM, Matthew Miller wrote:
Hi everyone! We have a new questions-and-help centered forum at https://ask.fedoraproject.org/ and I invite you to try it out.
I've been getting nothing but Error 503 Backend fetch failed and a Guru meditation from there for several days now.
That's the first report of this I've heard. Perhaps you have something cached which is sending you to the old DNS?
On 05/02/2019 11:14 AM, Matthew Miller wrote:
On Thu, May 02, 2019 at 10:18:22AM -0600, Joe Zeff wrote:
On 05/02/2019 08:50 AM, Matthew Miller wrote:
Hi everyone! We have a new questions-and-help centered forum at https://ask.fedoraproject.org/ and I invite you to try it out.
I've been getting nothing but Error 503 Backend fetch failed and a Guru meditation from there for several days now.
That's the first report of this I've heard. Perhaps you have something cached which is sending you to the old DNS?
Even after clearing my cache, I get that from Firefox, but Seamonkey picks it up OK.
Allegedly, on or about 2 May 2019, Joe Zeff sent:
Even after clearing my cache, I get that from Firefox, but Seamonkey picks it up OK.
Did you fully quit and restart Firefox? If not, it could be operating from something still in memory.
When a browser gets stuck in the past, there's two usual culprits:
* It's cached the files its downloaded, and won't fetch new versions (*often* you can simply reload the page, sometimes while holding a qualifier key down - like the SHIFT key).
* It's remembered the IP address that it connected to before, and won't check to see if the IP has changed (this has always required a full program exit, to clear, with my browsers).
I don't know whether, for either case, it's obeying the information it was told for how long it's permitted to cache the data (regardless of how impractical it may be), or ignoring it and following the browser programmer's ideas on what's best to do (regardless of how impractical that may be, too).
I wish browsers would acknowledge a user's reload instruction as: start completely afresh because something didn't work right.
On 05/02/2019 11:15 PM, Tim via users wrote:
Allegedly, on or about 2 May 2019, Joe Zeff sent:
Even after clearing my cache, I get that from Firefox, but Seamonkey picks it up OK.
Did you fully quit and restart Firefox? If not, it could be operating from something still in memory.
I did, after I found that a different browser worked. Not only did it fix that site, it fixed another one that had persisted in giving error messages after earlier restarts.
On 05/02/2019 11:15 PM, Tim via users wrote:
I wish browsers would acknowledge a user's reload instruction as: start completely afresh because something didn't work right.
There was a time when Shift-Reload would force it to get a new copy of everything, but that doesn't seem to make a difference anymore. And, to be honest, I've no idea if that made the browser do new DNS lookups as well.
On 3/5/19 3:01 pm, Joe Zeff wrote:
There was a time when Shift-Reload would force it to get a new copy of everything, but that doesn't seem to make a difference anymore.
I can't recall which browsers that worked with.
And, to be honest, I've no idea if that made the browser do new DNS lookups as well.
It probably never did.?? WWW IPs weren't really meant to change that much, so it never was much of a consideration.?? Doesn't help you, though, when working within a LAN, where IPs can be changed by automated systems for ill-considered reasons.
There seems to be a fundamental misunderstanding with browser programmers.?? They may think we just want to refresh because the page didn't layout logically, and it might do better if poked a bit.?? But under what circumstances is that actually a logical process??? If a page failed to render sensibly, usually that would be because either the browser is faulty, or some of the data is missing.
A page reload is far more likely to be used because the user has struck a failure, and wants to reset the page from scratch.
Though, in the past, with our tragically slow internet, repeatedly hitting refresh had been about the only way to get some pages to load.?? Our country having such a slow internet that some sites would simply abort with timeouts when pages had lots of images that couldn't fully load within the limits of its patience.?? If the whole thing didn't load within some stupidly quick timeframe, it'd cut you off.?? You'd have a page with half-loaded and unloaded images all over the place.
So browsers with a reload, and a more forceful shift-reload feature, were actually useful.
-
Joe Zeff -
Matthew Miller -
Tim