Re: Compression disabling on chunked response

Thanks Willy. Yes I can understand no-transform disabling it, I just wanted to make sure that chunked response no longer disables compression. It verifies my tests as well, thanks for confirming it. Thanks Sachin On Mon, Oct 8, 2018 at 11:00 PM Willy Tarreau wrote: > Hi Sasha, > > On Fri, Oct

Ambiguity in documentation for `http-request set-header`

The documentation for `http-request set-header` is a little ambiguous about whether it removes all occurrences of the header if it previously existed or just the first one. From experimentation it appears it is all occurrences (which I think is preferable). May I suggest rewording "except that

Re: faster than load-server-state-from-file?

Am 08.10.2018 um 19:35 schrieb Willy Tarreau: > On Mon, Oct 08, 2018 at 07:27:39PM +0200, Aleksandar Lazic wrote: >> Hi Baptiste. >> >> Am 08.10.2018 um 16:20 schrieb Baptiste: >>> Bonjour Messieurs, >>> >>> (je passe en FR et hors ML et je top-poste!!!). >> >> Just for my curiosity, why not

Re: faster than load-server-state-from-file?

On Mon, Oct 08, 2018 at 07:27:39PM +0200, Aleksandar Lazic wrote: > Hi Baptiste. > > Am 08.10.2018 um 16:20 schrieb Baptiste: > > Bonjour Messieurs, > > > > (je passe en FR et hors ML et je top-poste!!!). > > Just for my curiosity, why not answering in english? He thought he responded

Re: Compression disabling on chunked response

Hi Sasha, On Fri, Oct 05, 2018 at 12:38:15PM +0530, Sachin Shetty wrote: > Hi, > > I see this in the documentation: > > Compression is disabled when: > * ... > * response header "Transfer-Encoding" contains "chunked" (Temporary > Workaround) > * > > Is this still

Re: faster than load-server-state-from-file?

Hi Baptiste. Am 08.10.2018 um 16:20 schrieb Baptiste: > Bonjour Messieurs, > > (je passe en FR et hors ML et je top-poste!!!). Just for my curiosity, why not answering in english? Best regards aleks > Pierre, je suis déjà en contact avec plusieurs autres Pierre de chez Critéo > (le > prénom,

Re: TLS 1.3 options available with OpenSSL 1.1.1

On Mon, Oct 08, 2018 at 04:35:55PM +0200, Emeric Brun wrote: > > I have updated the documentation. Hopefully this is good then. Would it be > > possible to also backport this to 1.8 so that we could deploy a future 1.8 > > stable version with OpenSSL 1.1.1 in the future? > > > Indeed, 1.8 is

Re: faster than load-server-state-from-file?

Bonjour Messieurs, (je passe en FR et hors ML et je top-poste!!!). Pierre, je suis déjà en contact avec plusieurs autres Pierre de chez Critéo (le prénom, c'est un critère de recrutement chez vous???) En tant que "dev" et "mainteneur" du server state, je ne suis pas surpris pas la lenteur de

Re: [PATCH] MINOR: generate-certificates for BoringSSL

Le 03/10/2018 à 12:52, Emmanuel Hocdet a écrit : Hi, For generate-certificates, X509V3_EXT_conf is used but it's an (very) old API call: X509V3_EXT_nconf must be preferred. Openssl compatibility is ok because it's inside #ifdef SSL_CTRL_SET_TLSEXT_HOSTNAME, introduce 5 years after

Re: [PATCH] MINOR: generate-certificates for BoringSSL

Le 03/10/2018 à 12:52, Emmanuel Hocdet a écrit : Hi, For generate-certificates, X509V3_EXT_conf is used but it's an (very) old API call: X509V3_EXT_nconf must be preferred. Openssl compatibility is ok because it's inside #ifdef SSL_CTRL_SET_TLSEXT_HOSTNAME, introduce 5 years after

Re: TLS 1.3 options available with OpenSSL 1.1.1

Hi Lukas, > On 7 Oct 2018, at 14:18, Lukas Tribus wrote: > > There is one space too much in the beginning of the penultimate line > in the doc of "ssl-default-server-ciphersuites" (--> <--TLSv1.2 and > earlier, please check). Updated in the attached patch! Cheers, Dirkjan