June 10, 2009 02:39PM
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
Subject Author Posted

400 bad request

snacktime June 10, 2009 02:03AM

Re: 400 bad request

Dave Cheney June 10, 2009 04:33AM

Re: 400 bad request

snacktime June 10, 2009 02:13PM

Re: 400 bad request

snacktime June 10, 2009 02:39PM

Re: 400 bad request

Eden Li June 10, 2009 03:06PM

Re: 400 bad request

Dave Cheney June 10, 2009 10:47PM

Re: 400 bad request

snacktime June 12, 2009 07:35PM

Re: 400 bad request

Dave Cheney June 12, 2009 09:00PM

Re: 400 bad request

snacktime June 12, 2009 09:44PM

Re: 400 bad request

Dave Cheney June 12, 2009 10:22PM

Re: 400 bad request

snacktime June 13, 2009 06:29PM

Re: 400 bad request

Jim Ohlstein June 13, 2009 07:16PM

Re: 400 bad request

Rob Schultz June 13, 2009 07:19PM

Re: 400 bad request

snacktime June 12, 2009 09:12PM

Re: 400 bad request

Dave Cheney June 12, 2009 09:36PM

Re: 400 Bad request

Maxim Dounin September 14, 2011 07:14AM

Re: 400 Bad request

Francis Daly September 14, 2011 07:14AM

Re: 400 Bad request

Igor Sysoev September 14, 2011 11:32AM

Re: 400 Bad request

coviex September 14, 2011 01:45PM

Re: 400 Bad request

Igor Sysoev September 14, 2011 02:04PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 298
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready