Hi David, If you're in SQ state, it means the request never reached a server, so you can't have any response header value.
Baptiste On Thu, Apr 9, 2015 at 11:11 PM, David Birdsong <david.birds...@gmail.com> wrote: > Greetings, I hope the rewrite from C->Lua is going well... > > I'm looking to trace down a weird scenario that might be a bug. We're > running: 1.5.2. Our backend is configured w/ a 500ms timeout queue and we > consistent hash on uri for load balancing. > > For requests logged as termination 'SQ' that trigger the timeout queue, the > backend server logs show zero requests matching the request log, which is > expected. The head-scratching finding is that on many of the request logs > we're seeing header captures that indicate part of the response was read > back from the server, but the header values themselves would be pretty > unlikely given that we can match URLs to expected header values. > > ...really what we'd expect is an empty header capture on the timeout queue > request log lines. > > I combed through the release notes to see if this was fixed, but I wasn't > able to match any of the notes to this particular occurrence. For the time > being, we're stuck at 1.5.5 since 1.5.6 changes hashes for path-based > hashing. We're working on re-arranging our infra to not take such a hit were > our working set request hashing to be redrawn which will happen with >= > 1.5.6. > > If there's a fix for this, we could probably expedite some work-arounds that > would allow us to upgrade if necessary. > > Here's a snippet from our frontend/backend config: > https://gist.github.com/davidbirdsong/55152514acbd9f2dbc2d > > Thanks!
