Hey Joris, I appreciate the help...I am not sure I quite understand though, is there something I can configure in haproxy to resolve this? It is not just a Wordpress problem, I have other sites also that do not behave correctly when I put haproxy in front of them.
On Mon, Oct 5, 2015 at 8:22 AM, joris dedieu <[email protected]> wrote: > Hi, > > 2015-10-04 23:33 GMT+02:00 Daren Sefcik <[email protected]>: > > I am trying to make some requests go to specific backends but am finding > > that in certain backends that the url gets doubled up or otherwise > mangled, > > ie: > > > > request to frontend = http://my.company.com > > what the backend server ends up with = > > http://my.company.comhttp://my.company.com > > > > This does not happen in all of the backends, only a few...a wordpress > site > > This is typically what append when wordpress is invoked with a wrong > Host header. > It must match WP_SITEURL and WP_HOME > > Regards > Joris > > > comes to mind as a specific example. Since this does not happen on every > > single backend server I suspect it is instead something happening on the > > receiving server but since it only happens when I put haproxy in front > of it > > there is some connection between them. > > > > Can someone help me understand what haproxy is doing or how to fix this > from > > happening? > > Before anyone says it is varnish doing it I should say several of the > other > > backends using varnish work fine, it is only a few that get the url > messed > > up. > > > > TIA > > > > example ACL: > > > > acl acl_my.company.com hdr(host) -i my.company.com > > use_backend VARNISH_BKEND if acl_my.company.com >
