[Zope-dev] Re: SiteAccess: virtual host monster and setServerURL issue

[Joseph Wayne Norton]

Evan -

I agree with your statement, but the system is behaving differently.

The generated URLs should not have :80 in them and they do not
... rather they have :1080 included in the generated URLs although I
have specifed something as follows:

mod_rewrite result:
   
    proxy:http://localhost:1080/VirtualHostBase/http/www.foo.com/vtfs/www.foo.com/vdmn/prd/vstg/VirtualHostRoot/
[OK]

and zope/vhm is generating URLs of the form:

   http://www.foo.com:1080/

I believe the setServerURL method is using the port number from the
environment setup from the mod_proxy/mod_rewrite request.  I'm
currently using 1080 for zope (z2.py -w 1080).

- j

p.s. One more related question .... have you tried using
mod_proxy/mod_rewrite with zope's webdav source port (-W) and virtual
host monster?


At Tue, 10 Apr 2001 10:57:15 -0400,
Evan Simpson wrote:
> 
> From: "Joseph Wayne Norton" <norton@arseed.co.jp>
> > The correct virtual URL is not setup properly because the setServerURL
> > method is always picking up the port #1080 (via oldhost,oldport) from
> > the mod_proxy/mod_rewrite request environment even if HTTP_HOST does
> > not contain a port number.
> 
> This is deliberate.  Omitting the port number means "leave it alone".  If
> you want port 80 (the http default), you need to specify it.  Generated URLs
> will not have ":80" in them, since it *is* the default port.
> 
> Cheers,
> 
> Evan @ digicool & 4-am
>