On 7 March 2017 at 08:48:37, Christopher Faulet ([email protected]) wrote:
Thanks for these info. By checking how you named your trace filters, I guess you use the HTTP compression. If I'm right, I think I found a bug with the help of your logs. The bug is triggered when your HTTP server replies before the end of the request. I guess it always sends its 401 responses just after reading requests headers. So it is timing issue from the HAProxy point of view. This should work of course. If I'm right, the bug only appears when a filter is used. So a temporary workaround, waiting my fix, is to disable the HTTP compression. I'll try to fix it very soon, I just need to talk with Willy to do it the right way. I will keep you informed. -- Christopher Faulet Hi Christopher, Yes - you’re right, in our normal configuration the compression filter is enabled. I was able to continue replicating the issue even without the compression filter when testing/generating those logs, but that was with the trace filter enabled - so there was always a filter. When I remove all filters (both trace & compression) the issue doesn’t reproduce in my test environment any more, so I think your theory is correct. Thanks for tracking it down - much appreciated :) Jon
