Re: Issues with redirects for POST requests with payload

On Sat, May 6, 2017 at 11:13 AM, Ciprian Dorin Craciun wrote: > Hello all! > > In last weeks I've started encountering a problem, that for our > particular use-case is seriously breaking some of our sites, namely: > > * a client makes a POST request which has a

Re: reqrep syntax

On 9/5/17 8:26am, Holger Just wrote: > With a modern HAProxy (i.e. anything >= 1.6), you can just use > > http-request set-path %[path,regsub(^/static,/)] Brilliant, thanks. I spent 20 minutes trying to figure how to submit a patch for the documentation, but failed completely. Maintainers of

Re: haproxy not creating stick-table entries fast enough

On Mon, May 8, 2017 at 4:01 PM, Lukas Tribus wrote: > Hello, > > > Am 09.05.2017 um 00:38 schrieb redundantl y: > > I am running haproxy 1.5.18-3 on CentOS 7 and need to use the > > stick-table feature to make sure traffic for a specific user persists > > to a given server. > > >

Re: haproxy not creating stick-table entries fast enough

Hello, Am 09.05.2017 um 00:38 schrieb redundantl y: > I am running haproxy 1.5.18-3 on CentOS 7 and need to use the > stick-table feature to make sure traffic for a specific user persists > to a given server. > > Things work fine when connections come in slowly, however when there's > numerous

haproxy not creating stick-table entries fast enough

I am running haproxy 1.5.18-3 on CentOS 7 and need to use the stick-table feature to make sure traffic for a specific user persists to a given server. Things work fine when connections come in slowly, however when there's numerous simultaneous connections and a stick-table entry doesn't exist yet

Re: Automatic Certificate Switching Idea

Hello, Am 30.04.2017 um 22:16 schrieb Daniel Schneller: > Hi! > > Yes, you got it right. I have no idea if there are technical limitations in > the SSL library or other parts of the code that would make several > certificate/key pairs for the same domain infeasible. > > If there were hard

Re: reqrep syntax

Hi Ari, Aristedes Maniatis wrote: > In the manual [1] there is an example for using reqrep with syntax > like this: > > # replace "/static/" with "/" at the beginning of any request path. > reqrep ^([^\ :]*)\ /static/(.*) \1\ /\2 > > [...] > > Firstly, is there no better/cleaner way to

Re: Passing SNI value ( ssl_fc_sni ) to backend's verifyhost.

Hello, Am 08.05.2017 um 10:56 schrieb Daniel Schneller: > Just my 2c, I very much support Kevin’s argument. > Even though we are not (yet) verifying backends — because currently we > _are_ in a private LAN — we are planning to deploy parts of our > application to public cloud infrastructure

reqrep syntax

In the manual [1] there is an example for using reqrep with syntax like this: # replace "/static/" with "/" at the beginning of any request path. reqrep ^([^\ :]*)\ /static/(.*) \1\ /\2 But a typical http request looks like this: GET /haproxy-dconv/1.7/configuration.html

Re: [RFC][PATCHES] seamless reload

Hi Pavlos, On Sun, May 07, 2017 at 12:05:28AM +0200, Pavlos Parissis wrote: [...] > Ignore ignore what I wrote, I am an idiot I am an idiot as I forgot the most > important bit of the test, to enable the seamless reload by suppling the > HAPROXY_STATS_SOCKET environment variable:-( > > I added

Re: Compare against variable string in ACL

Holger, On 08.05.2017 11:37, Holger Just wrote: > We use basically this configuration snippet in production for quite some > years now and it works great. > while not exactly pretty, it definitely works fine. Thank you. Best regards Tim Düsterhus

Re: Compare against variable string in ACL

Hi Tim. Tim Düsterhus wrote: > I basically want an ACL that matches if 'hdr(host) == ssl_fc_sni' to use > programming language terminology. This is not directly possible right now using haproxy ACLs since they are only ablle to to compare a dynamic value (the fetch) to a static value. There is

Re: Passing SNI value ( ssl_fc_sni ) to backend's verifyhost.

Just my 2c, I very much support Kevin’s argument. Even though we are not (yet) verifying backends — because currently we _are_ in a private LAN — we are planning to deploy parts of our application to public cloud infrastructure soon, so it would be a quite important feature. Regards, Daniel