Page 1 of 1

11.2.11 - Certain sites produce Access Denied Page

Posted: Sun Oct 03, 2021 8:28 pm
by sparky
Certain sites such as vans.co.uk and dominos.co.uk load 403 access denied pages (but work in private browser sessions) even with all scripts allowed for that page/site. Haven't seemed to find a way around this or an answer on google, any help appreciated.

Re: 11.2.11 - Certain sites produce Access Denied Page

Posted: Mon Oct 04, 2021 6:40 am
by musonius
vans.co.uk works for me even with the default settings of NoScript, dominos.co.uk does not work even with NoScript disabled. Therefore, I assume that NoScript may not be the problem.

What happens, if you disable NoScript?

Re: 11.2.11 - Certain sites produce Access Denied Page

Posted: Mon Oct 04, 2021 8:32 am
by sparky
For me, if I disable noscript in firefox altogether, both sites work exactly as expected (I suspected as such as I only got noscript in the past couple of weeks and have used these sites in the past no problem). The behaviours I have noted with these sites is:

- both worked on first launch with noscript turned on but not after refresh (have seen from a google clear cache seems to work for first session and not again after)
- both work fine in firefox private browsing session (regardless of noscript settings)
- both show similar 403 access denied pages that I have never seen from other websites until installing noscript extension very recently

I'm quite new to the extension so I'm wondering if there is some setting that is blocking certain website types with certain types of Javascript? Even if i turn off all restrictions for the tab it still doesn't work or manually allow all scripts that I can see from the private browsing session. Only fully disabling the extension seems to fix...any ideas would be more than welcome.

Re: 11.2.11 - Certain sites produce Access Denied Page

Posted: Mon Oct 04, 2021 11:42 am
by HBK
I get the same problem.

Re: 11.2.11 - Certain sites produce Access Denied Page

Posted: Mon Oct 04, 2021 2:59 pm
by therube
Confirmed.
It's going to be the same (or similar to) access denied after firefox update.

Before Allowing https://www.vans.co.uk/, the page looked OK.

After Allowing https://www.vans.co.uk/:

Code: Select all

Access Denied
You don't have permission to access "http://www.vans.co.uk/403fail/" on this server.

Reference #18.146019b8.1633359400.56b01

Re: 11.2.11 - Certain sites produce Access Denied Page

Posted: Mon Oct 04, 2021 3:32 pm
by sparky
Thanks for pointing to the other thread. I did actually find that thread when looking for a solution before posting, but I'm not sure its actually resolved unless I'm missing something. From the other thread's investigation it seems as though it may not be a NoScript issue although the issue only seems to occur with NoScript turned on, so some combination of NoScript and a Firefox setting (that obviously isn't handled the same in private browsing mode) appears to cause the issue, I guess. If I've misunderstood the other thread though and there is a resolution please treat me like an idiot and explain it for me :D

Re: 11.2.11 - Certain sites produce Access Denied Page

Posted: Tue Oct 05, 2021 7:26 am
by skriptimaahinen
dominos.co.uk seems to throw the "Access Denied" for anyone coming from outside of UK. Site is accessible for me through UK based proxy, but didn't test any further as I suspect it works the same way as the vans.co.uk, which is:

If you visit the site with javascript disabled, it will set you a cookie that causes the "Access Denied" on any subsequent load.

Clearing this cookie will allow you to view the page again.

Having scripts enabled will get you another cookie that allows you to browse the page.

(blocking cookies for the page works too if you don't want to enable scripts)

@sparky: Is Noscript allowed on Private Browsing for you?

Re: 11.2.11 - Certain sites produce Access Denied Page

Posted: Tue Oct 05, 2021 8:38 am
by sparky
Thanks skriptimaahinen! As you said I tried a clear cookies etc with the site scripts already turned on for noscript and the websites now work and display as expected. Interesting quirk with the cookies but an easy fix for the future.

To answer your other question noscript is turned on for private browsing but as this was a cookies issue, probably explains why it worked there as each new private session would have a fresh cache wouldn't it?