On Fri, Jan 06, 2006 at 02:56:52PM +0100, Ortwin Gl?ck wrote: > > > Oleg Kalnichevski wrote: > >Odi, > > > >I have no problem with being wrong. The hard fact there's no such > >thing as a 'virtual' port in the HTTP spec, so I do not see a reason for > >inventing one. > > What would you call the optional port in the Host header then? If the > server was able to figure that out on its own it would not be necessary. >
The explicit port in the Host header is used in case the target port number is not equal to that of the default protocol port > > There is a clear-cut interface how to request resources > >from a target server via a proxy, which to my knowledge does not involve > >virtual ports either > > Please read the description of the ProxyPass directive in the Apache > HTTPD docs. It does not use the proxy protocol (the name is misleading). > It merely forwards the request to a different server and relays its > response to the client. Normally the two Apache processes are on the > same machine. Anyway that was just an example. I don't know what Jasper > is doing exactly. I fail to see any reference to the Host header in this directive http://httpd.apache.org/docs/2.0/mod/mod_proxy.html#proxypass Oleg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
