New
#1821
I looked around after I posted that and the closest an answer I can find is it may have to do with Akamai's CDN (Content Delivery Network) or some other CDN, here's from Tom's Hardware: An error occurred while processing your request | post #5:
All I did to fix it is add an 's' to the http in the link I had for the NWS site and that cured it. Then I took Callender's suggestion an installed the HTTPS Everywhere add-on from EFF and haven't had a problem since. Some of these CDN's may balk at sending a request through if they don't see that 's'.The following is what has been communicated to me from the devs, verbatim:
We're doing what we can to address the issue, but certain aspects are out of our control. It appears to mainly be affecting US West Coast users, which helps to narrow things down. The issue is being prioritized as a result of all the people it seems to affect, but I'm told that we should not expect any immediate resolutions to this. It seems as if this will take some time.What we know is that this bug is not directly our own, it rather looks like it lies under akamaï’s responsibility. Akamaï owns servers that serve our pages as a sort of ‘cache’, we use them in the US because it improves the page load performance.
Since this is not under our very own control, the investigation is taking a long time.
Check for the spurious 's' on your bookmark it may be your problem to unless beta 11 holds for you and Firefox figured it out, but TenForums has always been https so I don't know. You'd need something like wireshark to see if akamai or again some other CDN has a hand in, however minutely, with content delivery for 10F.
Ubuntu? That's not in my pay-grade, yet.
)
