[Zope] BASE and nonstandard ports (RE: [Zope] w3m (alternative to lynx) and Zope. ) and Zope. )

Terrel Shumway tshumway@epicor.com
Mon, 4 Oct 1999 12:36:54 -0700


BTW: Mozilla currently has the same problem with <base> and non-standard
ports.

What document should I refer to when reporting the bug? RFC ???

-----Original Message-----
From: Martijn Pieters [mailto:mj@antraciet.nl]
Sent: Sunday, October 03, 1999 10:36 PM
To: Anthony Baxter
Cc: Sascha Matzke; zope@zope.org
Subject: Re: [Zope] w3m (alternative to lynx) and Zope. 

Hmm.... that would indeed be the cause of the misbehaving BASE tag. 
HTTPRequest constructs the BASE either from HTTP_HOST, or, if omitted, from 
SERVER_NAME and SERVER_PORT.

You can confirm this by opening 
http://servername:serverport/path/to/Zope/REQUEST in w3m (in your case 
http://bespin:9090/REQUEST), and then look for the HTTP_HOST and SERVER_URL 
environment variables. If they read bespin, and not bespin:9090, then w3m 
is to blame and a bug report should be filed with its creator.