Date: Fri, 11 Feb 2000 16:01:33 -0500 (EST)
From: bpaulsen@lehman.com (Brian Paulsen)
Message-Id: <200002112101.QAA26982@g890.lehman.com>
To: bpaulsen@lehman.com, marc@locus.apache.org, apache-bugdb@apache.org
Subject: Re: general/5746
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-MD5: qiPm1gih7JAOfEfHaUF/dA==
Sender: apache-bugdb-owner@apache.org
Precedence: bulk

Hmm, that clears up a misunderstanding on my part, and you are absolutely
correct that the remaining problem is how to deal with the port issue.

Here's the final kicker (and I'm willing to jump into modrewrite unless
you know of a quick fix)...  I'm not always guaranteed to have port 80
be the default...

Here's what is happening:
I have my machine set up with a ServerName of `hostname` and somebody
else is proxying to it.  Unfortunately, these guys like to set up development
proxies and test them out and I have little control over what port they
want to use on their development proxy server.

So, unfortunately, I can't set up my machine to be on Port 80 and listen
to 8888.

In other words, what I need to handle are the following cases:
http://othermachine/mydirectory
and
http://othermachine:1000/mydirectory
and the generic
http://othermachine:XXXX/mydirectory

Is there a quick way in apache to handle this one, or should I be visiting
the modrewrite scripts?

Thanks,
Brian

> Synopsis: Troubles combining UseCanonicalName with DirectoryIndex
> 
> State-Changed-From-To: open->closed
> State-Changed-By: marc
> State-Changed-When: Fri Feb 11 12:22:11 PST 2000
> State-Changed-Why: 
> You have it backwards here; the canonical name is what the server thinks
> it is, not what the client does.  You want UseCanonicalName off.
> 
> That still won't deal with the port issue, so for that you need to make
> sure you set a "Port 80" directive and use a "Listen 8080" directive
> to tell Apache to actually listen to port 8080, while thinking it is
> on port 80.  
> 
> Note that the example URL you give won't show this problem, because you
> include a trailing '/'.  It only will if you don't include the trailing
> '/'.
>