Terrel Shumway wrote:

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.

RFC2068 Section 14.23: The Host request-header field specifies the Internet host and port number of the resource being requested, as obtained from the original URL given by the user or referring resource (generally an HTTP URL, as described in section 3.2.2). The Host field value MUST represent the network location of the origin server or gateway given by the original URL. This allows the origin server or gateway to differentiate between internally-ambiguous URLs, such as the root "/" URL of a server for multiple host names on a single IP address. Host = "Host" ":" host [ ":" port ] ; Section 3.2.2 -Michel

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(Related lists - please, no cross posts or HTML encoding!

To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce

For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )