On Tue, Aug 28, 2018 at 11:11:52AM +, Edward Hibbert wrote:
> This is partly a FAQ, but hopefully it goes beyond that...into a more subtle
> FAQ, perhaps.
>
> I understand that in general it is dangerous for haproxy to retry a request
> once it has been sent to a server, for example after a
Hi Tim,
On Tue, Aug 28, 2018 at 10:27:34PM +0200, Tim Düsterhus wrote:
> Willy,
>
> Am 25.08.2018 um 08:13 schrieb Willy Tarreau:
> > Done,thanks.
> >
>
> I just noticed that the reg-test still carried the old name (h*),
> instead of the new one (b*), because Frederic renamed them in the mean
Willy,
Am 25.08.2018 um 08:13 schrieb Willy Tarreau:
> Done,thanks.
>
I just noticed that the reg-test still carried the old name (h*),
instead of the new one (b*), because Frederic renamed them in the mean
time, while this patch still was pending. You should rename lua/h1.*
to
Hi Frederic,
Op 28-8-2018 om 11:27 schreef Frederic Lecaille:
On 08/27/2018 10:46 PM, PiBa-NL wrote:
Hi Frederic, Oliver,
Thanks for your investigations :).
I've made a little reg-test (files attached). Its probably not
'correct' to commit as-is, but should be enough to get a
reproduction..
On 08/14/2018 11:27 AM, Lukas Tribus wrote:
Hello,
Hi,
the "set server / fqdn " admin socket command
requires the internal DNS resolver to be configured and enabled for
that specific server. This is undocumented, and I will provide a doc
fix soon.
However, when the resolver is not
On Tue, Aug 28, 2018 at 02:47:28PM +0200, Olivier Houchard wrote:
> Ok you're right, I have a patch for that problem, which should definitively
> be different from Pieter's problem :)
> Willy, I think it's safe to be applied, and should probably be backported
> (albeit it should be adapted, given
Hi,
On Mon, Aug 27, 2018 at 03:26:50PM +0200, Frederic Lecaille wrote:
[...]
>
> According to Pieter traces, haproxy has registered HTTP service mode lua
> applets in HTTP mode. Your patch fixes a TCP service mode issue.
> reg-test/lua/b1.vtc script runs both HTTP and TCP lua applets. But
This is partly a FAQ, but hopefully it goes beyond that…into a more
subtle FAQ, perhaps.
I understand that in general it is dangerous for haproxy to retry a
request once it has been sent to a server, for example after a timeout
or error, because the server may not be idempotent. I get this
On 08/27/2018 10:46 PM, PiBa-NL wrote:
Hi Frederic, Oliver,
Thanks for your investigations :).
I've made a little reg-test (files attached). Its probably not 'correct'
to commit as-is, but should be enough to get a reproduction.. I hope..
changing it to nbthread 1 makes it work every
On 08/27/2018 10:46 PM, PiBa-NL wrote:
Hi Frederic, Oliver,
Hi Pieter,
Thanks for your investigations :).
I've made a little reg-test (files attached). Its probably not 'correct'
to commit as-is, but should be enough to get a reproduction.. I hope..
changing it to nbthread 1 makes it work
10 matches
Mail list logo