Over the last few days I’ve been having issues with the Folksy site when using Chrome. Sometimes it works fine for a while, then I will get this error if I click on my dashboard, or a link to an item:
400 Bad Request
Request Header Or Cookie Too Large
nginx/1.6.2
Once I get it then it keeps happening. I have cleared my cache/cookies and it doesn’t help. If I restart the browser it will work for a while, but after few minutes I get the error again. Im using a desktop, Windows 10 and Chrome.
I only have a problem with Folksy, no other sites, and if I change my browser to Edge (which I am not keen on) then it works ok.
Any advice?
According to the internet you might want to clear your DNS cache as well (different to your browser cache) How to Flush and Clear Windows DNS Cache
Also check that chrome is up to date.
Thanks Sasha @SashaGarrett.
Chrome is up to date.
I’ve cleared out the DNS cache, and it worked ok for about half an hour, and long enough to print out an order, but it’s now doing the error again.
Can you help Doug @dougfolksy ?
What are you doing before the error occurs? Internet says that a 400 error normally happens if there is a mistake in the url such as if a cookie has got corrupted.
I’m just clicking on something, like ‘dashboard’ from the drop down menu, or a link from a forum post. Sometimes I get to my dashboard, but I’ll get the error when I click on ‘listings’ or ‘orders’. It’s really bizarre how random it is.
I cleared my cache & cookies again and restarted my computer…it’s behaving at the moment so I’ll see how it goes.
Do you have any extensions or plugins set up on chrome? If you do then try turning them off. (I had an issue with a plug in causing a bit of Folksy to break but it was always the same bit not randomly like you are seeing but its worth a try)
Have been increasingly getting this message the last week or so. Mainly when I click on an item to visit the listing, whether that’s on the forum, my shop, or other shops on the folksy site. At the beginning it fixed itself without me doing anything, I eventually added the Folksy site to clear cookies every time I close my browser, but it doesn’t seem to have any difference. Had it twice already today and every time seems to last longer to the point I just close Folksy for a few hours.
I am on microsoft edge, never had problems before, and it’s only on Folksy, despite the clearing up of cookies at the exit. Any ideas?
I am getting the problems outlined by people above - I notice the last post was over a year ago but thought this was an appropriate place to post. When I go to my shop and click on an item, this is the message I get several times a day.
400 Bad Request
Request Header Or Cookie Too Large
nginx/1.6.2
I have never had problems previously, and it only happens on Folksy, not on other websites. If I clear my recent history, it works OK for a few hours, then I get it again, have to clear again and so on. It also happens sometimes if I click on an item in someone else’s shop, or even on trying to go to my shop from the main page. I use Firefox browser on a laptop. Anyone any ideas?
I have just noticed a separate thread with a post by @kimfolksy and following that advice I have now tried clearing cookies and data by clicking on the padlock on my Firefox browser. I will see if this does the trick.
Update 15/03/25 Yes it worked - I’ve not had any problems since!
I’ve been getting this 400 Bad Request message too over the last few days - cleared cache and cookies 3 times now which brings it back, but it’s very frustrating! Happening on PC using Chrome.
This was the reply from Kim that I tracked down and which worked for me. @PhotoFairytales
While there is a known issue that comes after a large amount of browsing and can be resolved by clearing the cookies, if anyone is persistently getting this after just clearing their cookies, can you please email support@folksy.co.uk, and let us know which browser and device you’re using (along with versions), and any other details which might seem important. Such as if you’d just cleared your cookies and it came up on one of the first pages you clicked afterwards, you’d done a lot of browsing in between or if you only get it on some pages but others are working.
As it’s not something we’ve managed to recreate ourselves yet, getting as much information as we can from those that are experiencing it can help us find a pattern to determine the cause.
Also, please note clearing the cache is NOT the same as clearing the cookies, although they can often be bundled together. For the known issue, it is the cookies that need clearing and just clearing the cached images and files will not fix it.
For those using a web browser, the quickest way to clear the cookies is usually to click on the symbol at the start of the address bar (for Chrome this is 2 lines with circles, for Firefox this is the padlock), where there should be an option to clear cookies and site data. This will specifically be for the site you’re currently on, so clearing the cookies for Folksy won’t log you out of any other sites.
Unfortunately we haven’t had much chance to look into issues like this over the past couple of months, but hopefully with more details and time we’ll be able to get this figured out and fixed.
Thanks Judy! I’ve looked at that button but can’t see the option to clear cookies just for Folksy? The dropdown I get offers “Cookies and Site Data” but when I click on that it just explains cookies and gives me an option to click through settings to clear ALL my cookies from all sites.
So instead, in Chrome I’ve gone to Settings > Privacy and Security > Site Settings - then clicked on View Permissions, found Folksy.com and cleared cookies just for the site. Fingers crossed that works this time, if not I’ll email support and let them know
Let me know if it works as I also use Chrome sometimes, but Firefox is my main browser. It still seems strange to me that I’ve never had the problem before, but I agree it really is irritating!
@PhotoFairytales It looks like how they show it might have become a little less obvious, but when you click ‘cookies and site data’ do you see ‘manage on-device site data’? If so click that and it should bring up Folksy and all the other cookies used on the site.
Then you just need to press the bin icon (if Google Analytics shows separately, make sure you do this as well as Folksy).
