Workaround for map_regm bug?

@sottolski wrote:

Hi there,

just tried to upgrade from 1.7.5 to 1.8.12, but was then bitten by a bug. My config has a map_regm directive to set a header, using a back reference; this doesn’t work any more, since the first character is being replaced by “00%”. A quick research seems to imply that it is a known problem, see

https://www.mail-archive.com/haproxy@formilux.org/msg30565.html

My map file looks lke

(.*)-somehost[1-9]\.domain\.com    \1                                                                                                                                                     
(.*)-otherhost[1-9]\.domain\.com    \1

Interestingly, I have another map file with backreference, and this seem not to have the “%00” problem:

.*-(somehost[1-9])\.domain\.com    \1
.*-(otherhost[1-9])\.domain\.com    \1

I’m using both for statements similar to

http-request set-var(txn.varname) var(txn.host_header),map_regm(/etc/haproxy/hostname.map)

obviously to extract parts of the FQDN. Not sure if it’s true, but it seems as if the bug only hits if the backrefence is about the beginning of the string to matched against.

I’m wondering how I could work around that bug. And, where would I report the bug, I couldn’t find a bug tracker for haproxy.

Thanks in advance

Sascha

Posts: 2

Participants: 2

Read full topic