On Thu, Oct 17, 2019 at 5:35 AM Daniel Corbett wrote:
> Hello,
>
>
> In #48 it was reported that when using the server-template
>
> directive combined with an SRV record that HAProxy would
> always set the weight to "1" regardless of what the SRV record
> contains.
>
> It was found that in an
Hello,
On 10/16/19 11:32 PM, Daniel Corbett wrote:
This patch should be backported to 1.8 and 1.9
Sorry, I forgot to indicate that this should be backported to 2.0 also.
Thanks,
-- Daniel
Hello,
In #48 it was reported that when using the server-template
directive combined with an SRV record that HAProxy would
always set the weight to "1" regardless of what the SRV record
contains.
It was found that in an attempt to force a minimum value of "1"
actually ended up forcing "1" in
Hi,
I did some more testing and found the reason why it didn't work:
I have added the required ip cmds:
post-up ip rule add fwmark 1 lookup 100
post-up ip route add local 0.0.0.0/0 dev lo table 100
post-up ip route add local ::/0 dev lo table 100
ip rule add fwmark
Previously an expression like:
path,field(2,/) -m found
always returned `true`.
Bug exists since the `field` converter exists. That is:
f399b0debfc6c7dc17c6ad503885c911493add56
The fix should be backported to 1.6+.
---
reg-tests/converter/field.vtc | 39 +++
Le 16/10/2019 à 08:48, GARDAIS Ionel a écrit :
Hi Christopher,
First : good news : I was not able to reproduce the issue with
2.1-dev2-e0f48a-88 and HTX enable.
I guess e0f8dc576f62ace9ad1055ca068ab5d4f3a952aa was the culprit.
To answer your questions and for others on the list :
- The issue
Hi Christopher,
First : good news : I was not able to reproduce the issue with
2.1-dev2-e0f48a-88 and HTX enable.
I guess e0f8dc576f62ace9ad1055ca068ab5d4f3a952aa was the culprit.
To answer your questions and for others on the list :
- The issue arose with H1 (H2 not enable)
- It's the client
7 matches
Mail list logo
