400 bad request

[Ninety5rpm]

For the first time today, I've been getting "400 bad request" errors when trying to access forum.cyclingnews.com. There is another line that says, "nginx/0.6.31". Otherwise, the page is blank.

On a lark I tried using Internet Explorer and this works, but I'm still getting the 400 errors using Google Chrome.

I've been successfully using Chrome for months without any such errors. It all started today.

I did get in a couple of times, but then it started generating these 400 errors again.

 

[Stelvio]

Me too, on and off since yesterday. On both www and forum. Since nginx is mostly used as a frontend proxy I would be surprised if the browser has anything to do with it . More likely someone has been fiddling with the config...

(But on checking I get more successful requests in a row with IE than I have got since yesterday with Firefox.)

 

[Animal]

Me too from FF.

In desperation I'm on Chrome now and putting up with in-page spam!

 

[Greg Johnson]

Please send screen shots to redesign@cyclingnews.com so we can look in to these issues.

Cheers
Greg Johnson

 

[Animal]

Working again from FF now.

 

[Stelvio]

@Greg:

 

[Ninety5rpm]

@Greg:

Yep, that's it.

I solved it (so far so good) by deleting all my cookies and logging back in.

 

[Ninety5rpm]

By the way, what information do you get from the screenshot that was not supplied in the first paragraph of the opening post to this thread?

 

[Stelvio]

I solved it (so far so good) by deleting all my cookies and logging back in.

That seems to have solved it for me too.