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.
Chris
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,2757,2787#msg-2787
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 that it's a bug with cookie headers.
chris
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,2757,2789#msg-2789
error_log /path/to/error.log info;
More: http://wiki.nginx.org/NginxHttpMainModule#error_log
On Wed, Jun 10, 2009 at 11:39 AM, snacktime<nginx-forum at nginx.us> wrote:
> 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 that it's a bug with cookie headers.
>
> chris
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,2757,2789#msg-2789
>
>
>