08-12-2023 03:32 PM
I can view it but logging in fails with "Bad Request - Header Field Too Long" & so can't post on my preferred Chrome. This has happened all day. It works on FF & Edge.
Solved! See the answer below or view the solution in context.
15-12-2023 10:35 AM
I understand that might be a bit of a pain, @XRaySpeX
Might be worth trying to clear the cookies out again to see if that resolves the issue before going for a full reinstall.
From what we can see, header too long error message is normally caused by a build up of cookies.
James
01-01-2024 02:56 AM
@James_B : Well I tried uninstalling & reinstalling Chrome but it made no diff. I could tell it was not a complete uninstall cuz when it came back it remembered all my settings, tabs & stuff.
I then discovered that if I switched to a diff Win. user on this PC, Chrome there allowed me to login to Community OK. So it must be something to do with my Win. user. I then found a whole wodge of Chrome user data (not the program) within my User folder on Win. So I just went ahead & deleted it to Recycle Bin. Now Chrome allows me to login to Community OK. BUT of course I lost all my settings, tabs & stuff.
Now I'll have to try & find a short way to reconstruct them w/out spoiling my login to Community.
01-01-2024 10:27 PM - edited 01-01-2024 10:31 PM
I had to introduce my useful tabs manually 1 by 1 but otherwise it's fixed!
1 benefit it produced was reduction of memory usage which had been troubling me when running many browsers & tabs at once.