varnish/apache wacky incorrect port issues when link contains atrailing slash
openbsdnow at gmail.com
Tue Feb 7 22:09:38 CET 2012
> On Tue, Feb 7, 2012 at 9:51 PM, Andreas Plesner Jacobsen <apj at mutt.dk
> <mailto:apj at mutt.dk>> wrote:
> On Tue, Feb 07, 2012 at 12:46:25PM -0800, Kevin wrote:
> > Tried setting it globally first and for fun at the VirtualHost
> > level, too, with the same results, :8080 in any of our URLs when
> > the trailing / is omitted.
> > As much as I hate to say it, this is a show-stopper for me right now
> > with getting Varnish in play in our environment.
> > Anyone have any other ideas?
> Run apache on port 80. We usually bind apache to 127.0.0.1:80
> <http://127.0.0.1:80> where backend and
> varnish runs on the same machine.
> That, and/or perhaps look at the description of the option
> UseCanonicalPhysicalPort (
> ) to be clear about the rewriting of Apache port number.
For better or worse, we're still using Apache 1.3, and this isn't/wasn't
an option in 1.3 (I already looked). :-(
> Also, please make sure that the redirection was not cached by Varnish.
I'm killing the daemon and restarting it each time I test. As far as I
know, this completely kills the cache, right? Or is there something else
I need to be doing, too?
More information about the varnish-misc