Welcome to nginx!

[oldborn]

The two issues aren't related, and don't worry - there should be no risk to your computer by visiting the site.

By the way, I can honestly say I've never such fun responding to a bug report.

Bug report, it is computer dying report here!
Really? How comes that I can not open many documents no more? And what about that red screen are you blind?
No risk to my computer, you are one funny dude josnor

 

[ramjambunath]

Oldborn-

Linux pingu is waiting.

 

[oldborn]

Try http://www.malwarebytes.org/ I have had great success with it

It works krebs, ngnix disappeared for now Havetts thanks too

 

[krebs303]

 

[mewmewmew13]

Krebs and Havetts saved oldborn!!!


red screen of death gone!

 

[krebs303]

 

[mewmewmew13]

the center of the universe

 

[Susan Westemeyer]

I just had a report from someone who is totally unable to get into the forum becuase of nginx. Anyone else having problems?

(obviously you can't answer if you can't get into the forum........)

Susan

 

[mewmewmew13]

I just had a report from someone who is totally unable to get into the forum becuase of nginx. Anyone else having problems?

(obviously you can't answer if you can't get into the forum........)

Susan

Susan, is it oldborn?

 

[Susan Westemeyer]

No, it wasn't, as a matter of fact.

Susan

 

[ElChingon]

Is all I get:


400 Bad Request
nginx/0.6.31

 

[josnor]

Is all I get:


400 Bad Request
nginx/0.6.31

Our operations team has hopefully sorted this problem. Let us know if you have any more issues connecting to the forum.

 

[ElChingon]

Our operations team has hopefully sorted this problem. Let us know if you have any more issues connecting to the forum.

Had to clear all my CN cookies to get it to work again so what ever you did had no sorting in the problem or solution.

So basically I set my cookie monster to eat your cookies when I shut down my browser so if it messes with your stats/tracking/identification, oh well.

 

[josnor]

Had to clear all my CN cookies to get it to work again so what ever you did had no sorting in the problem or solution.

So basically I set my cookie monster to eat your cookies when I shut down my browser so if it messes with your stats/tracking/identification, oh well.

That's the other solution. The trouble is that vBulletin (the forum software we're running) likes to set huge cookies and Firefox doesn't limit them when they get sent to the server, which isn't set up to handle such large cookies and so you get the HTTP 400 response. We've upped the limits which should hopefully be enough for most users.