httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Slive" <>
Subject Re: [users@httpd] self-referential URL's and load balancer
Date Mon, 12 Jun 2006 23:18:50 GMT
On 6/12/06, enigma <> wrote:
> I have a problem with the self-referential URL's being generated by Apache
> when a hardware load balancer is front ending it.
> The load balancer listens on port 443, decrypts SSL and forwards standard
> http to Apache on port 13443 on the culster machines. The problem I
> encounter is when Apache generates self-referential URL's for mod_dir
> trailing slash redirects and mod_rewrite redirects, it is sending the
> protocol as http and the port as 13443. So for instance, the brower
> requests:
> The redirect returned by Apache is:
> which is invalid on the load balancer and no longer SSL.
> I want it to be:
> I have tried setting UseCanonicalName Off without success. I can remap the
> port with the port directive, but it still changes the https to http.
> Any suggestions??

We had an almost identical question two days ago (see below).
Unfortunately, I don't believe there is any way to fix this completely
from the apache side short of using the unreleased svn-head version of
apache which allows the scheme to be specified with the ServerName

On 6/11/06, Damian Birchler <> wrote:
> Hi all
> I have got Squid installed as an httpd accelerator for httpd. Squid will
> not allow requests to other than per SSL/TLS. Squid
> itself talks to httpd in plain text. Now, when httpd generates automatic
> redirects -- what I mean by this, is for example redirecting /foo to /foo/
> -- it tells the client to try HTTP:// which is
> then blocked by Squid.
> So, my question: Is it somehow possible to customize automatic redirects,
> for instance by telling httpd to use only relative paths?

Relative paths are not legal in redirects.  Squid probably has the
capability to rewrite these headers itself (as apache's mod_proxy can
do with the ProxyPassReverse directive).  Otherwise, you can tell
apache to lie about its true hostname using the ServerName and
UseCanonicalName directives.  But you will still have a problem with
the scheme.  The latest development version of apache allows you to
configure ServerName to lie about the scheme, but I don't think any
released version can do that.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message