On Fri, Jan 06, 2006 at 02:02:08PM +0100, Ortwin Gl?ck wrote: > > > Oleg Kalnichevski wrote: > >Jasper, I believe I can vaguely tell the difference between numbers > >80 and 100. The point I am trying to make is that there is no such > >thing as a 'virtual' port. The target server either listens on a port > >or it does not. Take a look at the HTTP spec. There is no mentioning > >of the concept of a virtual port in it > > > >Oleg > > You may be wrong here, Oleg. The Host header may contain a port number. > The spec only says this port number must match "the resource being > requested, as obtained from the original URI given by the user or > referring resource". That's not necessarily the port the server is > listening on. Imaging a cascade of Apache servers that forward requests > using the ProxyPass directive. > > Jasper, can you explain the scenario in which you are encountering the > need for this feature? > > Odi >
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. 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 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]
