[PATCH] BUILD: ssl: include buffer common headers for ssl_sock_ctx

since commit c0cdaffaa338 ("REORG: ssl: move ssl_sock_ctx and fix cross-dependencies issues"), `struct ssl_sock_ctx` was moved in ssl_sock.h. As it contains a `struct buffer`, including `common/buffer.h` is now mandatory. I encountered an issue while including ssl_sock.h on another patch:

Re: [PATCH] enable arm64 builds in travis-ci

Hi Willy, On Fri, May 15, 2020 at 6:07 PM Willy Tarreau wrote: > Ilya, > > > also, I'd suggest to purge travis-ci cache (if you are build in your own > > fork). > > some travis related issue might be related when something is took from > > cache (which was not supposed to happen) > > Could you

Re: [External] Re: [RFC PATCH] Improved moving averages

Great, thanks WIlly. Enjoy! :-) Marcin Deranek On Sat, May 16, 2020 at 10:40 PM Willy Tarreau wrote: > Hi Marcin, > > On Sat, May 16, 2020 at 04:31:30PM +0200, Marcin Deranek wrote: > > Actually I split this into 3 (see attachments): > > 1. Adds improved swrate_rate_dynamic function > > 2.

Re: [PATCH] enable arm64 builds in travis-ci

Thank you for applying the patch! The ARM64 build passed at https://travis-ci.com/github/haproxy/haproxy/jobs/335338296 ! But it passes only for the builds which have 'haproxy-mirror' : https://travis-ci.com/github/haproxy/haproxy/builds I am not sure what exactly "haproxy-mirror" is in the

Re: decode key created with url32+src

Tim. Thank you for your prompt answer. Regards Aleks On 18.05.20 01:30, Tim Düsterhus wrote: > Aleks, > > Am 18.05.20 um 00:48 schrieb Aleksandar Lazic: >> Is there a easy way to know which URL+src the key is? >> [...] >>   http-request track-sc1 url32+src table per_ip_and_url_rates unless {

Re: decode key created with url32+src

Aleks, Am 18.05.20 um 00:48 schrieb Aleksandar Lazic: > Is there a easy way to know which URL+src the key is? > [...] >   http-request track-sc1 url32+src table per_ip_and_url_rates unless { > path_end .css .js .png .gif } No, as per the documentation: > url32+src : binary > This returns the

decode key created with url32+src

Hi. I have this lines in the Table per_ip_and_url_rates. Is there a easy way to know which URL+src the key is? # table: per_ip_and_url_rates, type: binary, size:1048576, used:56781 0x559813fc9200: key=xxx use=0 exp=85821390 http_req_rate(8640)=27 0x7fef40373630: key= use=0 exp=86380499