Re: [squid-users] Reverse proxy with 2.6 and several backends with different ports

On Mon, 2007-07-02 at 09:10 +0200, Emilio Casbas wrote:

> The same rewrite rules are working with squid-2.5 but no with squid-2.6.
> Is there any workaround to solve this?

Then had the accelerator mode configured differently, probably

httpd_accel_host internal.server.name
and NOT
httpd_accel_uses_host_header

this translates to

http_port 80 defaultsite=internal.server.name

> Could you be a little more specific with some situation where a rewrite
> rule would be strictly needed and another one where it wouldn't be?

A rewrite rule is strictly needed if the backend server can not accept
the real URL.

A rewrite rule is not needed at all if the backend server can accept the
real URL.

You SHOULD NOT use rewrite rules for routing purposes. Use
cache_peer_access for that.

It is highly preferred to have things set up in such manner that the
backend servers is given the real requested URL. HTTP servers returns
their view of the URL in a number of places, and fixing them all up if
the servers view and the actual Internet use differ is quite messy.

Regards
Henrik