• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Bad Request error using Google Chrome

Status
Not open for further replies.

Quartz-1

Supreme [H]ardness
Joined
May 20, 2011
Messages
4,257
I'm getting a lot of Bad Request errors from Hardforum when using Google Chrome version 33.0.1750.154 m. The error is

Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.
Cookie
/n

I've seen the error typically after doing a search for subscribed threads then clicking on a thread, but also simply trying to access this forum. The problem comes and goes. I'm experiencing it right now, but last night was fine, as was earlier today, but earlier yesterday was not. I'm writing this with IE 11 which works fine. I'm not having any issues with other message boards.
 
Same here.

It's exactly what it says. Cookie value gets really huge.

Deleting the bad cookie fixes the problem.
 
Well yes, but which cookie was it? I deleted all the Hardocp and hardforum cookies and I'm now working, but I don't want the problem to recur in 6 months or so.
 
I don't think it's a single cookie in particular, actually. The server probably barfs when the cookie header gets too large.

The amount of data passed is absurd.
 
I've never had this issue using Firefox. I looked through the cookies for hardforum and found one that is much longer than any of the others:
hhthread_lastview
It's pretty obvious what that cookie does. In my case, its content is 1040 characters long:
bba110683794ea12bdce45205f1e8d6583b1c28ea-43-%7Bi-1813667_i-1396502063_i-1615187_i-1396480423_i-1812774_i-1396538548_i-1813603_i-1396659756_i-1812100_i-1396713975_i-1813691_i-1396539001_i-1813720_i-1396543191_i-1813702_i-1396544430_i-1795614_i-1396647757_i-1808099_i-1396542484_i-1813717_i-1396546340_i-1813726_i-1396548424_i-1813739_i-1396568386_i-1813731_i-1396559953_i-1813862_i-1396622475_i-1813950_i-1396661254_i-1813967_i-1396670575_i-1813890_i-1396672175_i-1813965_i-1396669068_i-1226866_i-1396713457_i-1811566_i-1396718777_i-1814012_i-1396719071_i-1814006_i-1396717927_i-1813993_i-1396717279_i-1813998_i-1396717607_i-1813980_i-1396714026_i-1813789_i-1396713812_i-1813838_i-1396710469_i-1810963_i-1396710369_i-1813835_i-1396708052_i-1814014_i-1396752152_i-1814013_i-1396726638_i-1814030_i-1396760260_i-1814026_i-1396729696_i-1814047_i-1396741528_i-1814050_i-1396746371_i-1814062_i-1396758053_i-1813537_i-1396766166_i-1814068_i-1396764834_i-1813829_i-1396758758_i-1807460_i-1396752667_i-1813391_i-1396752410_i-1814071_i-1396787558_%7D

When Googling for "400 bad request" errors, the usual advice seems to be that either a cookie got corrupted and the solution is to delete it, or that the file that stores cookies for your particular browser got corrupted and needs to be deleted.
 
Was seeing it here last week. Deleting the [H] cookies was the only fix. Only does it on CHrome on desktop I think....Mobile Chrome doesn't do it.
 
I made a change to apache, as this issue isnt reproducible for me using chrome.
 
Most browsers have a limit of around 4096 bytes per cookie. My hhthread_lastview cookie is the closest to that limit at 4048 bytes.
 
I was getting a ton of these today, cleared my cookies and it seems to be fixed.
 
Same thing here. It happens when I click any link that goes to lucca.hardforum.com (all the rewritten links posted in threads).

EDIT: Clearing my cookies resolved the issue.
 
Last edited:
Came here to post the same thread/issue. Glad to have found that clearing the cookies fixes it. Worked for me. Thanks!
 
Status
Not open for further replies.
Back
Top