Hello Aleks and Tim, Thank you for your insightful guidance on the usage of http-request and http-response in our context.
We are updating the config files—several of them--along the lines you have suggested. We will test it and will push it into production shortly. Thank you. Sincerely, Hemant K. Sabat www.Coscend.com <http://www.coscend.com/> ------------------------------------------------------------------ Real-time, Interactive Tele-healthcare, Tele-education, Telepresence Services, on the fly… ------------------------------------------------------------------ CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages from Coscend Communications Solutions' posted at: http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html -----Original Message----- From: Tim Düsterhus [mailto:t...@bastelstu.be] Sent: Thursday, November 28, 2019 3:14 AM To: Aleksandar Lazic <al-hapr...@none.at>; Coscend@HAProxy <haproxy.insig...@coscend.com> 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- > request%20replace-uri > > I would try this. > http-request replace-uri /CoscendP/*([^\ ]*)\ (.*)$ /\2\ \3 > > >> http-response replace-header ^(Location:)\ (https?://([^/]*))/(.*)$ >> Location:\ /CoscendP/\3 > > I would use this as the header name isn't a regex. > > http-response replace-header Location (https?://([^/]*))/(.*)$ > Location:\ /CoscendP/\3 > > http://cbonte.github.io/haproxy-dconv/2.1/configuration.html#4.2-http- > request%20replace-header > FYI: You made the same mistake I made. You forgot to adjust the numbers of the capturing groups in the replacement after removing the first one from the regex. Best regards Tim Düsterhus
