Doors wrote:
On Sun, 19 Jul 2020 12:28:36 +0100,
mozilla-lists.mbou...@spamgourmet.com wrote:

Doors wrote:
On Sat, 18 Jul 2020 19:15:39 +0100, "Nuno Silva"
<nunojsilva@invalid.invalid> wrote:
Any chance this one said the following?:

"Access Denied

You don't have permission to access "[address]" on this server.

Reference #[number].[number].[number]"



That'd be blacklisting by Akamai:

https://security.stackexchange.com/questions/197753
https://news.ycombinator.com/item?id=15688362

That looks correct.
Confusing part is I could pull up the same page on FF no problem.
That was annoying.
Fail on SM, work on FF, same address, same minute.
Load root of newegg, works.
Go anywhere on site, fail.

Really started bugging me.

Do you block JavaScript, or use an extension which blocks it, on
SeaMonkey?  I had similar issues some time ago with a couple of sites I
use, with NoScript in my case blocking scripts by default.  I think they
turned out to be using Akami.  Allowing the domain to run scripts
resolved the problem.

It was no good loading the site and then temporarily allowing scripting
for it though, as they seemed to decide on loading the first page that I
was going to be blocked for any further requests (even just reloading
the home page I was already looking at lead to access denied).  As I
recall, I think I could enable scripting and then delete cookies set for
the domain, so seems something was stored in cookies on that first load,
which caused the problem for subsequent requests even if scripts were
then enabled.  But it was easier to just permanently allow JavaScript
for those domains.

I rebuilt the profile by creating a clean one, then manually importing
pieces one by one.
Now it works, but no idea why.

My plugins are simple.

DOM inspector, epubreader, restart, show password, & umatrix.

Everything is the same as it was before, only now it works.
Really weird.

I'd suspect something different in the configuration of uMatrix between the two profiles. That allows you to control which sites can run scripts (amongst other things). I thought it blocked scripts by default, but perhaps somehow in your new profile it's allowing scripts to run for the sites you have problems with, while in your old profile it's blocking them (or perhaps one of the other things it blocks).

--
Mark.

_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to