Re: [PATCH] use forward-proxy port for internal URLs

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Fri, 15 Jul 2011 15:33:17 +1200

On 10/04/11 19:24, Amos Jeffries wrote:
> alters the getMyPort() function to skip ports flagged for special mode
> handling (intercept, tproxy, accel) when generating internal URLs.
>
> This allows us to lock down security on these special mode ports and
> still have an arbitrary position for the forward-proxy port. Prior to
> this only the first port was used, forcing an unnecessary configuration
> order.
>
> Since it is now possible to have no port available for these URLs the
> fatal()/crash has been reduced to an annoying cache.log message. Port 0
> will be inserted into the URLs making them invalid.
>
> For now this is only done on http_port entries. https_port has an
> incomplete merge of https_port_list/http_port_list which needs to be
> completed before it is easily done there.

Applied.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.14
   Beta testers wanted for 3.2.0.9
Received on Fri Jul 15 2011 - 03:33:23 MDT

This archive was generated by hypermail 2.2.0 : Fri Jul 15 2011 - 12:00:04 MDT