Hi.
Am 24.08.2018 um 11:04 schrieb Daniel Schneller:
> Hi!
>
> Thanks for that input. I would like to understand what's going before making
> changes. :)
There is a how-it-works.txt
http://git.haproxy.org/?p=haproxy-1.8.git;a=blob;f=doc/design-thoughts/how-it-works.txt;h=2d1cb89a059e477469b2f980
Hi!
Thanks for that input. I would like to understand what's going before making
changes. :)
Cheers,
Daniel
> On 24. Aug 2018, at 00:56, Igor Cicimov
> wrote:
>
> Hi Daniel,
>
> We had similar issue in 2015, and the answer was: server timeout was too
> short. Simple.
>
> On Thu, 23 Aug 2
Hi Daniel,
We had similar issue in 2015, and the answer was: server timeout was too
short. Simple.
On Thu, 23 Aug 2018 9:56 pm Daniel Schneller <
daniel.schnel...@centerdevice.com> wrote:
> Friendly bump.
> I'd volunteer to do some documentation amendments once I understand the
> issue better :D
Friendly bump.
I'd volunteer to do some documentation amendments once I understand the issue
better :D
> On 21. Aug 2018, at 16:17, Daniel Schneller
> wrote:
>
> Hi!
>
> I am trying to wrap my head around an issue we are seeing where there are
> many HTTP 504 responses sent out to clients.
>
Hi!
I am trying to wrap my head around an issue we are seeing where there are many
HTTP 504 responses sent out to clients.
I suspect that due to a client bug they stop sending data midway during the
data phase of the request, but they keep the connection open.
What I see in the haproxy logs is
5 matches
Mail list logo