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.