Hello Jonathan,
Greetings for the day,
Please find the Front-end and Back-end of Ha-Proxy configuration details in
the attachment.
Kindly let us know if there is any amendments.
Mit freundlichen Grüßen / With Best Regards,
Gokulakrishnan.R
Gsep-Crosscutting
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
Daimler AG
Global Software Engineering Platform (GSEP)
Incident/Query: GSEP
Webticket<https://cism-web.es.corpintra.net/cgi-bin/bin/runTemplate?TP=web_ticket&t=GSEP-Support>
Requirements: Submit a GSEP
Demand<https://gsep.daimler.com/jira/secure/CreateIssue%21default.jspa>
From: Jonathan Matthews <cont...@jpluscplusm.com>
Sent: Tuesday, July 14, 2020 2:26 PM
To: R, Gokulakrishnan (623-Extern-MicroGenesis) <microgenesi...@daimler.com>
Cc: haproxy@formilux.org; Ramavarapu, Krishna Chaitanya
(623-Extern-MicroGenesis) <microgenesis.ramavar...@daimler.com>
Subject: Re: Ha-proxy ignoring context after first digit
On Tue, 14 Jul 2020 at 08:47,
<microgenesi...@daimler.com<mailto:microgenesi...@daimler.com>> wrote:
We are using Ha-proxy 1.8. Recently we started facing issue with Ha-Proxy
ignoring context after first digit.
Do you perhaps mean “Host” rather than Context?
Please check and help us on this.
Whilst I’m not ruling out a bug in haproxy causing this, it is *vastly* more
likely that this is either inadvertently caused by your haproxy configuration
or another layer 7/HTTP device in your traffic flow.
Please post the smallest haproxy config which exhibits this issue so folks can
help you figure it out!
J
--
Jonathan Matthews
https://jpluscplusm.com
If you are not the addressee, please inform us immediately that you have
received this e-mail by mistake, and delete it. We thank you for your support.
frontend http_gsep-int_in
bind :80
mode http
http-request deny if { path -i -m beg /stash } { src 53.55.88.99 }
http-request deny if { path -i -m beg /crowd } { src 53.55.88.99 }
http-request deny if { path -i -m beg / } { src 53.55.88.99 }
acl path_mtc-jenkins-1 path_beg /mtc-jenkins-1
use_backend mtc-jenkins-1_1564 if path_mtc-jenkins-1
acl path_mtc-jenkins-2 path_beg /mtc-jenkins-2
use_backend mtc-jenkins-2_1565 if path_mtc-jenkins-2
acl path_mtc-jenkins-6 path_beg /mtc-jenkins-6
use_backend mtc_application_zone6 if path_mtc-jenkins-6
acl path_mtc-jenkins-7 path_beg /mtc-jenkins-7
use_backend mtc_application_zone7 if path_mtc-jenkins-7
acl path_mtc-jenkins-8 path_beg /mtc-jenkins-8
use_backend mtc_application_zone8 if path_mtc-jenkins-8
acl path_mtc-jenkins-9 path_beg /mtc-jenkins-9
use_backend mtc_application_zone9 if path_mtc-jenkins-9
acl path_mtc-jenkins-10 path_beg /mtc-jenkins-10
use_backend mtc_application_zone10 if path_mtc-jenkins-10
default_backend apache_servers
################################################################################
backend apache_servers
server server1 127.0.0.1:81 maxconn 32
backend mtc-jenkins-1_1564
# http-request set-header X-Forwarded-Proto https
# http-request set-header X-Forwarded-Port 443
server mtc-jenkins-1 53.55.88.100:8080 check
backend mtc-jenkins-2_1565
server mtc-jenkins-2 53.55.88.99:8080 check
backend mtc_application_zone6
server mtc-jenkins-6 53.55.112.187:8080 check
backend mtc_application_zone7
server mtc-jenkins-7 53.55.112.186:8080 check
backend mtc_application_zone8
server mtc-jenkins-8 53.55.112.185:8080 check
backend mtc_application_zone9
server mtc-jenkins-9 53.55.112.184:8080 check
backend mtc_application_zone10
server mtc-jenkins-10 53.55.112.183:8080 check
