Hi.
I plan to use HAProxy 1.9.x cache with ~50-100k Objects which will could use
1-2G RAM.
Have anyone used the cache features in prod with such specs?
The Idea is to use HAProxy in AUS for a Webserver in FR for caching as the
latency delays the delivery from FR to AUS Clients.
Thank you for
On Tue, Jan 29, 2019 at 04:38:56PM +0100, Tim Duesterhus wrote:
> Willy,
>
> new patch with the requested changes and updated tests.
>
> Note: I added an `assert` in there to make sure that ht*_select_comp_reshdr
> actually verified the ETag header before I am touching it. There *is*
>
On Tue, Jan 29, 2019 at 12:56:14PM +0100, Tim Düsterhus wrote:
> I just notice the `http_select_comp_reshdr` function. I guess I can put
> the ETag validation there and only check for strong / weak in
> `http_set_comp_reshdr`.
Yes, good idea!
Willy
Hi Luke,
On Tue, Jan 29, 2019 at 10:52:15AM +, Luke Seelenbinder wrote:
> Hi Willy,
>
> > By the way, how do you manage to cancel a single stream in the browser ?
> > Pressing Esc might break all of them I guess ? Thus I'm uncertain how to
> > achieve this.
>
> So we're in a very specific
Willy,
new patch with the requested changes and updated tests.
Note: I added an `assert` in there to make sure that ht*_select_comp_reshdr
actually verified the ETag header before I am touching it. There *is* precedence
for `assert` in `checks.c`. Please remove the `assert` if you are not happy
On Tue, Jan 29, 2019 at 10:25:15AM +0200, Elena Sarimichailidou wrote:
> Hello Willy,
>
> Thank you for replying so fast. The department in the organization I belong
> to is managing Security so this is why I asked you so.
> How can we informed about new version announces and stay up to date?
Hello Willy,
Thank you for replying so fast. The department in the organization I belong
to is managing Security so this is why I asked you so.
How can we informed about new version announces and stay up to date?
Thank you
Elena
On Tue, Jan 29, 2019 at 5:27 AM Willy Tarreau wrote:
> Hello
On Tue, Jan 29, 2019 at 10:41:52AM +0100, Louis Chanouha wrote:
> I'm pretty sure this bug is specific to version 1.9. Last week i restarted
> the process because is seemed to be stuck at around 100% CPU, but without
> anormal behaviour.
> I've never saw that in 1.7 or 1.8 series. We migrated from
Hi Willy,
> By the way, how do you manage to cancel a single stream in the browser ?
> Pressing Esc might break all of them I guess ? Thus I'm uncertain how to
> achieve this.
So we're in a very specific use-case of delivering map tiles, which are
predominately requested via Leaflet.js.
January 29, 2019 4:24:57 AM CET Willy Tarreau wrote:Hello Louis,
On Mon, Jan 28, 2019 at 10:43:37PM +0100, Louis Chanouha wrote:
> Hello,
> We faced this evening a critical issue this issue where all agent-checks
ware
> stuck (or retries very very slower than usual).
> In example I see "2h39m
Hi all,
I'm observing some odd behavior with seamless reloads and processes hanging
around. It appears when a reload is triggered with any active client
connections, the new process comes up with the proper -sf , but the
old process(es) is only terminated after the last client disconnects
Hi Luke,
On Tue, Jan 29, 2019 at 10:06:03AM +, Luke Seelenbinder wrote:
> I just pulled, compiled, and tested the newly minted 1.9.3, and I'm
> experiencing the same issue with alpn h2 on the backend definition.
Ah sh*t :-(
> I also
> strongly suspect it's not related to maximum streams per
Hi Willy,
> As you like. My first rule is never to make people take risks they're not
> willing to take. It's perfectly OK to me if you don't feel confident with
> 2.0-dev in prod. I'm going to perform the 1.9 backports. If you're
> interested in testing them from the branch before I release it
On Tue, Jan 29, 2019 at 11:39:32AM +0100, Willy Tarreau wrote:
> By the way, how do you manage to cancel a single stream in the browser ?
> Pressing Esc might break all of them I guess ? Thus I'm uncertain how to
> achieve this.
I think I found a solution for this, I open two tabs in the browser
Hi Luke,
On Tue, Jan 29, 2019 at 10:31:00AM +, Luke Seelenbinder wrote:
> Hi all,
>
> I'm observing some odd behavior with seamless reloads and processes hanging
> around. It appears when a reload is triggered with any active client
> connections, the new process comes up with the proper -sf
Willy,
Am 29.01.19 um 04:05 schrieb Willy Tarreau:
>> FWIW: I have no idea what that "Warning header" in configuration.txt is. Do
>> you
>> have any idea?
>
> I have a vague memory about an old suggestion to update the Warning header
> when applying content transformations. Just found it, it's
Hi William,
> The timeout client applies on inactivity, are you sure those connections are
> inactives? Try to do a "show sess" on the old process so you can see the
> remaining sessions.
I suspected the same. This confirms what I observed.
> Are you using the seamless reload feature or just
Hi, all
HAProxy 1.8.17 on Ubuntu 18.04.
The relevant configuration is trivial:
frontend
mode http
option httplog
bind 1.2.3.4:443 name HTTPS ssl crt /etc/ssl/private/full.pem
ssl-min-ver TLSv1.2 alpn h2,http/1.1
timeout client 1m
use_backend onboard
backend onboard
mode http
Am 29.01.2019 um 06:52 schrieb Willy Tarreau:
> Hi,
>
> HAProxy 1.9.3 was released on 2019/01/29. It added 35 new commits after
> version 1.9.2.
>
> It mainly addresses a few stability issues affecting versions up to 1.9.2.
> Several of these issues are only reproducible when using H2 to connect
Willy,
Am 29.01.19 um 12:47 schrieb Tim Düsterhus:
> I initially implemented it as a `goto error`. That disables the actual
> compression of the body. Unfortunately the `Content-Encoding` header is
> already modified, thus the client expects gzip, but receives plain data.
> I could mitigate that
20 matches
Mail list logo
