On Tue, Jun 18, 2019 at 12:57:58AM +0200, Cyril Bonté wrote:
> Le 16/06/2019 à 21:56, Willy Tarreau a écrit :
> > Hi,
> >
> > HAProxy 2.0.0 was released on 2019/06/16. It added 63 new commits
> > after version 2.0-dev7.
> > [...]
> >
> > Please find the usual URLs below :
> > Cyril's HTML
Le 16/06/2019 à 21:56, Willy Tarreau a écrit :
Hi,
HAProxy 2.0.0 was released on 2019/06/16. It added 63 new commits
after version 2.0-dev7.
[...]
Please find the usual URLs below :
Cyril's HTML doc : http://cbonte.github.io/haproxy-dconv/
And with more than 24h later, I've deployed the
On Mon, Jun 17, 2019 at 04:10:07PM +0200, Tim Duesterhus wrote:
> Make HAProxy set the `Vary: Accept-Encoding` response header if it compressed
> the server response.
(...)
Perfect, now merged, thank you Tim!
Willy
Make HAProxy set the `Vary: Accept-Encoding` response header if it compressed
the server response.
Technically the `Vary` header SHOULD also be set for responses that would
normally be compressed based off the current configuration, but are not due
to a missing or invalid `Accept-Encoding`
Hi,
For reason now obscured by history, VTest has a (relative) timestamp
on every line of its output:
*** v1 27.4 CLI RX 300
v1 27.4 CLI RX|Cannot set the active VCL cold.
** v1 27.4 CLI 300
** top 27.4 === varnish v1 -cliok "vcl.state vcl1
On Mon, Jun 17, 2019 at 02:33:05PM +0200, Tim Düsterhus wrote:
> > So in my opinion we should only emit "Vary: accept-encoding" when
> > adding Content-Encoding. Am I missing something ?
>
> I believe you are correct that only sending the 'Vary' when actually
> compressing is fine according to
Willy,
Am 17.06.19 um 14:17 schrieb Willy Tarreau:
> Hi Tim,
>
> I'm back to this one :
>
> On Wed, Jun 12, 2019 at 10:36:51PM +0200, Tim Duesterhus wrote:
>> This thread contains two "competing" patches to fix the BUG that HAProxy
>> does not set the `Vary` response header when the compression
Hi Tim,
I'm back to this one :
On Wed, Jun 12, 2019 at 10:36:51PM +0200, Tim Duesterhus wrote:
> This thread contains two "competing" patches to fix the BUG that HAProxy
> does not set the `Vary` response header when the compression filter is
> applied. When not setting the `Vary` header the
On Fri, Jun 14, 2019 at 09:59:23PM +0200, Baptiste wrote:
> Let's sync after the release.
Second patch now merged!
Willy
On Mon, Jun 17, 2019 at 12:41:44PM +0200, Tim Duesterhus wrote:
> This adds a converter for the SHA-2 family, supporting SHA-224, SHA-256
> SHA-384 and SHA-512.
(...)
Merged, thanks Tim!
Willy
Am 16.06.2019 um 21:56 schrieb Willy Tarreau:
> Hi,
>
> HAProxy 2.0.0 was released on 2019/06/16. It added 63 new commits
> after version 2.0-dev7.
[snipp]
> Please find the usual URLs below :
>Site index : http://www.haproxy.org/
>Discourse: http://discourse.haproxy.org/
This adds a converter for the SHA-2 family, supporting SHA-224, SHA-256
SHA-384 and SHA-512.
The converter relies on the OpenSSL implementation, thus only being available
when HAProxy is compiled with USE_OPENSSL.
See GitHub issue #123. The hypothetical `ssl_?_sha256` fetch can then be
simulated
Hello dinchak.com,
Hope you are doing well!
While doing a preliminary analysis on your
website dinchak.com, I have discovered the current design standards. Your
website can be enhanced in a way to make it more productive.
However, I have prepared a Website
Re-Design/Development proposal for
14 matches
Mail list logo