Hi,

>> One last thing to try: can you remove the "timeout http-request"
>> completely from the configuration and retry?
>>
> done. still got 408.
>
> I tried removing it on both 1.4 and 1.5dev22

Try removing "timeout client" as well (never ever do this in production).
You will see a startup warning, ignore it and test if you still can
reproduce it.

Without "timeout http-request" and "timeout client" you probably don't see
this issue.

However you cannot run like this in production.

Also try setting "timeout client" to a huge value like 120m just for test
purposes (con't configure "timeout http-request" for the time being).


I suggest you try this an different box, not virtualized or on a different
hypervisor as well. I still think what you are experiencing is time jump
related.



Regards,

Lukas                                     

Reply via email to