Well I figured out exactly what causes this after getting someone that had the errors to install the firefox livehttpheaders plugin. It's the cookie size. Cookie too large, nginx returns a 400 and doesn't log it. Unfortunately there isn't much we can do about the cookie size. With the fb connect iframe stuff there are other parties setting cookies on our domain. I tried in the past uppingby snacktime - Nginx Mailing List - English
Dave Cheney Wrote: ------------------------------------------------------- > So, to confirm, there is no record of the request > at all in your > access log? Nothing. I set the log level on the error log to debug also to see if that would force something into the error logs, but nothing. But facebook is telling you that it > could not contact your > servers (sorry,by snacktime - Nginx Mailing List - English
I just turned up the error log level to debug and nginx still won't log these. It's definitely generating them though.by snacktime - Nginx Mailing List - English
nginx doesn't log these errors for some reason. They don't show up in the access or error log, and we have both turned on. If I could look at the raw data I could figure out if it's facebook that's breaking a spec somewhere, or if it's an nginx bug. We have narrowed it down to being specifically a cookie issue. More specifically it's facebook connect that sets the cookies nginx bombs on.by snacktime - Nginx Mailing List - English
Is there a way to force nginx to log 400 errors? At least then I could debug this better. It's been difficult to find specific triggers. The one common trigger is that it only happens in a facebook connect iframe. We have a situation where two facebook connect iframes are loaded from our domain on the same page, and that triggers it around 80% of the time. My best guess at this point is thatby snacktime - Nginx Mailing List - English
It's not mongrel, although I dont' know for sure if mongrel wouldn't also choke on whatever nginx is choking on if nginx actually passed it through. Chrisby snacktime - Nginx Mailing List - English
this is nginx 0.6.34. We run some fairly high volume facebook sites and have had problems with 400 errors now for months. It only happens on one part of our site that runs inside an iframe. At first I thought it was cookies that were too large. I increased some of the buffers but that didn't appear to make any difference. A couple of days ago we took out all the code that was generating largeby snacktime - Nginx Mailing List - English