28, 2019 3:14 AM
To: Aleksandar Lazic ; Coscend@HAProxy
Cc: haproxy@formilux.org
Subject: Re: Seeking Guidance: 2.1.0 Config Error
Aleks,
Am 27.11.19 um 22:36 schrieb Aleksandar Lazic:
> This should be replace-uri
> http://cbonte.github.io/haproxy-dconv/2.1/configuration.html#4.2-http-
&
Aleks,
Am 27.11.19 um 22:36 schrieb Aleksandar Lazic:
> This should be replace-uri
> http://cbonte.github.io/haproxy-dconv/2.1/configuration.html#4.2-http-request%20replace-uri
>
> I would try this.
> http-request replace-uri /CoscendP/*([^\ ]*)\ (.*)$ /\2\ \3
>
>
>> http-response replace-head
Hemant,
Sorry, I forgot to adjust the capturing groups. There is an off-by-one
in my examples.
Am 27.11.19 um 22:39 schrieb Tim Düsterhus:
> http-request replace-uri ^/CoscendP/*([^\ ]*)\ (.*)$ \1\ /\2\ \3
This should read:
http-request replace-uri ^/CoscendP/*([^\ ]*)\ (.*)$ /\1\ \2
> http-re
Hemant,
Am 27.11.19 um 21:37 schrieb Coscend@HAProxy:
> 2.0.9 config line that worked:
>
> reqirep ^([^\ ]*)\ /CoscendP/*([^\ ]*)\ (.*)$ \1\ /\2\ \3
>
> rspirep ^(Location:)\ (https?://([^/]*))/(.*)$Location:\
> /CoscendP/\3
>
> Corresponding 2.1.0 config line that gives erro
Hi.
Nov 27, 2019 9:38:35 PM Coscend@HAProxy :
>
> Dear HAProxy Community,
>
>
>
> We are upgrading from 2.0.9 to 2.1.0. Accordingly, we have to replace:
>
> · reqirep with http-request and
>
> · resprep with http-response.
>
>
>
> We are getting the following two errors.
>
> Error 1: 'http-requ
Dear HAProxy Community,
We are upgrading from 2.0.9 to 2.1.0. Accordingly, we have to replace:
.reqirep with http-request and
.resprep with http-response.
We are getting the following two errors.
Error 1: 'http-request replace-header' expects exactly 3 arguments.
Hi,
Am 12.04.2016 um 19:39 schrieb Shawn Heisey:
I copied a front end to set up a new service on my haproxy install. I
changed the name of the front end, but forgot to change the port number
on the "bind" option.
Haproxy didn't complain about this configuration when I tested for
validity, so
On 12.04.2016 21:11, Baptiste wrote:
> On Tue, Apr 12, 2016 at 7:39 PM, Shawn Heisey wrote:
>> I copied a front end to set up a new service on my haproxy install. I
>> changed the name of the front end, but forgot to change the port number
>> on the "bind" option.
>>
>> Haproxy didn't complain ab
On 4/12/2016 1:11 PM, Baptiste wrote:
> This is not an error, this type of configuration is valid. You should
> write a script which check this on your own.
I know it's not a config error, and I would not want effective behavior
in any current versions to be changed. The mistake wa
On Tue, Apr 12, 2016 at 7:39 PM, Shawn Heisey wrote:
> I copied a front end to set up a new service on my haproxy install. I
> changed the name of the front end, but forgot to change the port number
> on the "bind" option.
>
> Haproxy didn't complain about this configuration when I tested for
> v
I copied a front end to set up a new service on my haproxy install. I
changed the name of the front end, but forgot to change the port number
on the "bind" option.
Haproxy didn't complain about this configuration when I tested for
validity, so I didn't realize I'd made a mistake until the origina
On 2010-02-19 13:31, Laurent DOLOSOR wrote:
Hi,
Hi,
I'm testing Haproxy 1.4-rc1, but I have a config error so ... strange.
I used this short config file. It works with Haproxy 1.3.23
http://pastebin.dinhosting.fr/9885
But with Haproxy 1.4-rc1, it returns the error :
[ALERT] 049/1
Hi,
I'm testing Haproxy 1.4-rc1, but I have a config error so ... strange.
I used this short config file. It works with Haproxy 1.3.23
http://pastebin.dinhosting.fr/9885
But with Haproxy 1.4-rc1, it returns the error :
[ALERT] 049/132313 (13531) : proxy 'fr2': stats 'aut
On Wed, Jan 13, 2010 at 08:47:00PM -0800, Craig Carl wrote:
> That cleared up the error, thanks Ryan.
>
> FYI I took that config straight out of the documentation -
> http://haproxy.1wt.eu/download/1.3/doc/architecture.txt
thanks for pointing it and sorry for this. I remember having
fixed them i
That cleared up the error, thanks Ryan.
FYI I took that config straight out of the documentation -
http://haproxy.1wt.eu/download/1.3/doc/architecture.txt
3.1. Alternate solution using Stunnel
===
Is the documentatio
Craig,
It looks like you're trying to specify the listen section's bind as its
name. I think this is what you want:
listen www 64.164.194.16:80
(Any name will work in place of www).
Ryan
On 01/13/2010 08:09 PM, Craig Carl wrote:
All -
I have a simple config using stunnel. I am trying to l
16 matches
Mail list logo
