My understanding is that this is really a client issue, rather than server. By the time a connector gets it, it's too late to do much about it.
A little bit of research indicates that the user agents I have about will put the IP address in the Host header if the URI is specified by IP. That seems the only reasonable thing to do. The name of the host in that case is the IP address. I suppose that if you were doing something bizzare like HTTP over a unix domain socket you wouldn't have a host name of any kind. But that's pretty far out there. But, on the TC side, I don't think the connector should rewrite the header if it's empty. On Wednesday 28 August 2002 12:26 pm, Ryan Lubke wrote: > Hi, > > Looking for a little input from the HTTP gurus here. > > Given the following: > > "If the requested URI does not include an Internet host > name for the service being requested, then the Host header > field MUST be given with an empty value." > > So, I'm looking for other interpretations of what the above means. > > My interpretation at this point is the serviced targeted by the > request URI is identified via an IP address vs a host name, that > the Host request header will be sent but with an empty value. > > Does anyone agree/disagree? > > The reason I ask is that if an empty Host header is sent to Tomcat, and > a redirect is sent back, the value of the Location header is useless, > i.e. http:///index.jsp. > > I'm trying to determine if this is a problem with the client > implementation's interpretation of the spec, or a problem with Tomcat. > > Thanks, > > -rl -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
