Spurious Error 403
I am a pensioner in te UK. Due to restricted mobility I spend a lot of time using Firefox to access many web sites. This normally works perfectly. Today I tried to access the web site of national chain store specialising in outdoor clothing and equipment because I need a new showerproof jacket. I have never used that site before, yet Firefox reported Error 403 : Forbidden. Have you people never been told tat error messages are supposed to be useful? What is Forbidden. Why when it has not happemed before?
The web site is https://www.millets.co.uk/
I have a web site so I have other browsers just for checking for layout problems.
I tried Chromium, same error but the message said You are not authorised to access this site. Presumably that is what your incompetent message should have said. But why should a pensioner trying to buy something from a chain store ever need any sort of authorisation?
I tried Opera. Connected me no problem!
I tried Edge. Connected me no problem.
Clearly somebody somewhere is an incompetent idiot, but it isn't me. So who is it? If it is yourselves then please do something to fix this.
Alle Antworten (9)
Hi
I can access that website with no problem.
Clear all saved data (menu > Settings > Privacy & Security > Cookies and Site Data > Manage Data...) for millets.co.uk
and/or try accessing the site with your add-ons temporarily disabled via Troubleshoot Mode (menu -> Help -> Troubleshoot Mode...).
Hmm. If I just delete the cookies, (which were not there to start with as my first visit failed) then I get through to the site. But as soon as I try to set my cookie preferences the error immediately occurs.
If I then repeat that but in troubleshoot mode that works.
If I restart Firefox again, presumably I'm no longer in troubleshoot mode, then I get access OK.
Presumably that means Millet's have a problem with their cookie setting process, yes?
A 403 error appears if you are not authorized to access a URL and the site doesn't elegantly redirect you to the login page to resolve the issue.
d.lazenby said
Hmm. If I just delete the cookies, (which were not there to start with as my first visit failed) then I get through to the site. But as soon as I try to set my cookie preferences the error immediately occurs. If I then repeat that but in troubleshoot mode that works. If I restart Firefox again, presumably I'm no longer in troubleshoot mode, then I get access OK. Presumably that means Millet's have a problem with their cookie setting process, yes?
How do you set your cookie preferences?
Like I said, this morning was the first time ever I visited the site and I got the 403 error immediately before anything else happened. Then after following the first part pf the previous instructions, I got on to the site and was given the typical set your cookie prefernces dialog which prevents any actual access. I selected the option to change my preferences. That gave me a dialog where Essential Only was the default. So I saved that. and got a 403. I then repeated the suggested process including the trouble shooter part. This time it worked OK.
But I have since discovered it is unstable. I started to click on a few things and then got anotherr 403.
REMEMBER, other browsers got me on to the site no problem.
I also have an old Windows 7 Tablet. That got me on no problem first time with Firefox! The problem only occurs on my Windows 11 PC!
So something newish is involved.
The fact that the problem disappears when you use Troubleshoot Mode (which disables extensions) maybe there is a conflict with an Add-on/Extension installed on your Windows 11 Firefox.
Start by disabling any extension related to privacy, ad-blocking, or cookie management and test.
Now I'm comfused! I had a spasm of finger trouble doing that. Restored everything one at a time and nothing caused the problem. But that is not good news as the Millet's cookie stopped being recorded! I not sure I believe the Settings report because one of my settings was being remembered on the web site!
So, it is bed time in here in th UK, so I'm going to bed and start from scratch tomorrow and see what happens with a clean sheet.
Watch this space!
I try things and sometimes I get a 403 when everything is enabled. So I disable everything and put them back one at a time to find the culprit. But everything works! Sometimes, as noted above, the Millet's cookie sometimes does not get re-created having deleted it unless I close and re-open Firefox.
Worse, if having found some action on the web site that retriggers the 403, then after disabling everything and incrementally re-enabling everything without getting a 403, then when I try to re-trigger the 403 the same way, it doesn't happen!
This is all too unstable to make sense of, so I guess we may have to close this down. However, as the only definite conclusion is that the problem has something to do with Addons etc, here is the list of what I'm using,
- WIKI 2. Wikipedia Republished
- Flash Player 2021
- Duckduckgo search box extention
- DuckDuckGo Privacy Essentials
- uBlock Origin
- Opt-out for Analytics
If there is any of those that you have previously found to be dodgy in some way without being able to precisely nail it down, then please tell me. In my own cynical way, with no evidence whatsoever, I would suspect the last one purely on the grounds it relates to Google and I don't trust Google!
So thanks all for trying. If you agree I'll then I'll close this.
> 4. DuckDuckGo Privacy Essentials
Is that this one? https://addons.mozilla.org/firefox/addon/duckduckgo-for-firefox/
This would be my top candidate for site breakage. The extension toolbar button provides a switch to turn protection on/off for specific sites, so that would be easier to toggle than enabling/disabling the extension as a whole.
The different name suggests otherwise but it would be strange if they had two tools doing the same job. Following sundry links for both I haven't found any use of "the other name" which would confirm them to be the same. Having said that, following your link gets me to a page with a Remove button and no others which you would think means they are the same. And what I have has exactly the switch you describe. On balance then it looks like they are the sane thing despite the lack of a smoking gun to prove it. Why is nothing simple? I've always kept my software simple, it's not rocket science.
Anyway, I'll turn it off for Millet's. Not that that will be definitive proof as getting to cause the 403 to occur is getting seriously hard.
Thanks.