Christopher,
Am 19.11.20 um 11:47 schrieb Christopher Faulet:
> Le 19/11/2020 à 10:49, Tim Düsterhus, WoltLab GmbH a écrit :
>> John,
>>
>> Am 19.11.20 um 06:57 schrieb John Lauro:
>>> A couple of possible options...
>>> You could use tcp-request inspect-delay to delay the response a
>>> number of
Le 19/11/2020 à 10:49, Tim Düsterhus, WoltLab GmbH a écrit :
John,
Am 19.11.20 um 06:57 schrieb John Lauro:
A couple of possible options...
You could use tcp-request inspect-delay to delay the response a number of
seconds (and accept it quick if legitimate traffic).
I believe the tcp-(request
John,
Am 19.11.20 um 06:57 schrieb John Lauro:
> A couple of possible options...
> You could use tcp-request inspect-delay to delay the response a number of
> seconds (and accept it quick if legitimate traffic).
I believe the tcp-(request|response) rules only apply to the very first
buffer of a s
A couple of possible options...
You could use tcp-request inspect-delay to delay the response a number of
seconds (and accept it quick if legitimate traffic).
You could use redirects which will have the clients do more requests
(Possibly with the inspect delays).
That said, it would be useful to f
Lukas,
Am 17.11.20 um 17:37 schrieb Lukas Tribus:
>>> is it possible to reliably disable client keep-alive on demand based on
>>> the result of an ACL?
>>>
>>> I was successful for HTTP/1 requests by using:
>>>
>>> http-after-response set-header connection close if foo
>>>
>>> But apparently that
Hi Tim,
On Tue, 17 Nov 2020 at 13:35, Tim Düsterhus, WoltLab GmbH
wrote:
>
> Hi
>
> Am 09.11.20 um 12:36 schrieb Tim Düsterhus, WoltLab GmbH:
> > is it possible to reliably disable client keep-alive on demand based on
> > the result of an ACL?
> >
> > I was successful for HTTP/1 requests by using
Hi
Am 09.11.20 um 12:36 schrieb Tim Düsterhus, WoltLab GmbH:
> is it possible to reliably disable client keep-alive on demand based on
> the result of an ACL?
>
> I was successful for HTTP/1 requests by using:
>
> http-after-response set-header connection close if foo
>
> But apparently that ha
Hi List
is it possible to reliably disable client keep-alive on demand based on
the result of an ACL?
I was successful for HTTP/1 requests by using:
http-after-response set-header connection close if foo
But apparently that has no effect for HTTP/2 requests. I was unable to
find anything within
8 matches
Mail list logo