Erik T. Brandsberg wrote:
> As for the users where there is no host field (remember, it
> doesn't strip or change the host field, just the http:// more
> matches the desired host), then sites that require a host
> field will never work anyway--because they operate on the host field.
Well.. a properly implemented Host: based virtual server takes care of
this. There is numerous howtos on how Host: based virtual servers should
be designed without breaking older clients, and it requires very little
work.
> The rewrite ONLY applies when the request itself starts with "/",
> i.e. it isn't a proxy style request to start with, and will TRY
> to use the host field. One IP/Multi servers works fine as every
> domain gets cached unto itself, and the "bad" requests without a
> host field will be cached by themselves.
Correct. For true (non-transparent/acceleration) proxy request this
problem does not exists, since the URL does not need any rewriting. The
URL host part and the Host: header should always be consistent (unless
someone is using a broken client or transparent proxy).
Received on Wed Dec 10 1997 - 00:56:22 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:37:54 MST