Hi,
We need per domain (not per frontend / backend) custom error pages.
Using an external error pages service seems required because operators
don't want/have to manage these fancy custom error pages.
Is there a way to add a dynamic param ( we just need something like
?c=503&h=%[hdr(host)] )
Your patch fix this issue, thanks !
Stéphane
On 29 May 2018, at 14:50, Olivier Houchard wrote:
> Hi Stéphane,
>
> On Tue, May 29, 2018 at 12:38:40PM +0200, Stéphane Cottin wrote:
>> Hi,
>>
>> This simple test config file :
>>
>> resolvers myd
Hello William,
Thanks for the patch, but applying it on 1.8.9 does not fix my issue.
Stéphane
On 29 May 2018, at 13:24, William Dauchy wrote:
Hello Stephane,
On Tue, May 29, 2018 at 12:38 PM, Stéphane Cottin
wrote:
This simple test config file :
resolvers mydns
nameserver ns1 10.0.0.1
Hi,
This simple test config file :
resolvers mydns
nameserver ns1 10.0.0.1:53
listen mysql
bind unix@/tmp/mysql.sock user www-data mode 600
option mysql-check user haproxy post-41
server MYSQL mysql.my.domain:3306 maxconn 100 check resolvers
mydns
makes hap
Hi,
A blog article about hot reloading configurations.
https://www.clever-cloud.com/blog/engineering/2017/07/24/hot-reloading-configuration-why-and-how/
This company was using haproxy, and because of reloading configuration
problems, among other aspects, they switch to their home made open
so
On 18 May 2017, at 6:36, Willy Tarreau wrote:
> Hi Stéphane,
>
> On Thu, May 18, 2017 at 02:31:07AM +0200, Stéphane Cottin wrote:
>> patch attached.
>
> Nice, that was fast :-)
Nobody have time, I just take care of things as they flow :)
>
> The patch looks p
Hi Willy,
On 17 May 2017, at 20:54, Willy Tarreau wrote:
Hi Stéphane,
On Wed, May 17, 2017 at 02:03:26AM +0200, Stéphane Cottin wrote:
Thanks, this is the right answer, recompile with
DEFINE=-DREQURI_LEN=4096
fixes this issue.
that's what I was going to say :-)
This limit shou
orra wrote:
On 16.05.2017 19:23, J. Kendzorra wrote:
On 16.05.2017 15:58, Stéphane Cottin wrote:
Only the content of "GET /?test=my_very_long_request_truncated" is
truncated to 1024 characters, not the whole line.
The end quote is still present, it does not seems related to syslog
daemon li
on options to
extend this limit. So you can either use another log daemon, or
re-compile syslogd with a higher limit, here's one example:
http://bsdpants.blogspot.com/2010/08/truncated-syslog-messages.html
Cheers,
-Mark
On Tue, 16 May 2017 07:28:30 -0400, Stéphane Cottin
wrote:
Hi,
Hi,
Version: haproxy 1.7.2
I'm logging to a unix socket, allowing long lines.
log /dev/log len 8192 local0
[...]
option dontlognull
option log-separate-errors
option httplog
I'm also capturing the referer header.
capture request header Referer len 4096
When using large strings (len
10 matches
Mail list logo
