Well, they both work… but they look rather different.

Puzzling.

I don't know if it's the same problem or linked, Michael, but a few weeks ago, I could get onto the TW site on my mobile phone, but as soon as I opened an article or comment, it gave me the bad request.

It seems to have fixed itself now.

Michael, it seems that the redirect wasn't working temporarily which can easily happen when using services like Google for 'security' certificates or DNS.

They even managed to lose their own South African webpage a few years ago as someone forgot to extend a certificate... so when you pay nothing, you can't expect much stability or security.

I am getting it a lot. Switching from Chrome to Safari seems to help. I just tried your workaround and that helps too.

The full message I get says "Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit."

No idea what that means, but something on the site seems not to play nice with Chrome? For me homepage works fine, but any link within site on Chrome and I get that error.

Go to your browser, settings, more settings and clear cache. You probably need to do this every few months

I am 74 this year, Michael, so do not ask me anything about the web.

I am technically challenged enough with dash-cams, video door bells and even GPS in car!!!!!!!!!!!!!!!!!!!!

There's a link to the Tom Fellows story that is on NewsNow at 07:48 this morning.

When I clink on the NewsNow link in Edge and in Chrome from my laptop, it works. When I do it in Chrome on my phone... "Bad Request"

I clear my browsing history and try again. "Bad Request".