AIBU to be annoyed with "400 Bad request" instead of threads actually loading?

[PortalooSunset]

Just that. Posted on a thread. Can see last responses only. Click previous page - 400 bad request. Click show all posts - 400 bad request. Click OP posts only - 400 bad flaming request.

Gah. Happening a lot at the moment. Really irritating. Is it just me?

YABU - it's just you and yoir crappy phone
YANBU - it happens to me too

Just you I think. Not me anyway.

Ironically (or not) I didn't see your reply last night @Justkeeppedaling because I didn't even know the thread had posted. As I hit post it went to 400 bad request again .
Tried updating/reinstalling Chrome but it's still doing it. Very frustrating.

A 400 bad request error is client-side, meaning something on your end triggered the error. When the server can’t understand a request you’ve made, it returns this error message.

Hi OP I get this all the time so I contacted mumsnet and was told to go to chrome then into incognito and that has worked for me give it a try

It got better for a while, but since Tuesday if I use Chrome in normal mode (and not incognito as I'm using now) every time I try and click on a thread/active/threads I'm on I get this error.
I appreciate what @flossyfloss432 is saying about it being an error my end but Mumsnet is the only website I have this issue with.
Thanks for the incognito tip @Margaretmatcher it's a bit of a faff but at least I can see something!

Managed to open my bookmarked 'Telly Addicts' link on normal Chrome but it was covered with this black box that popped up. No idea how/why because I have pop ups blocked 🤔
It's really very frustrating. Any way of sorting it?? {mention:JustineMumsnet}?@JustineMumsnet??

No idea but fir the past few months I can't order in Ocado on Chrome. It gives be a page saying there is a clear up in aisle 5. That's supposed to be a cute way to say there us an error. I have to use safari. Maybe chrome is shit

I have the same problem on Chrome and have to use another browser.

Whilst accepting it is client side, I do not have this issue with any other sites, and didn't have the problem before MN was replatformed so I think there is something in the way the site load that causes the issue.

I've had this since the update. It's very annoying!