On Sun, 2010-02-07 at 00:52 +1300, Amos Jeffries wrote:
> According to the W3C documentation the Surrogate/1.0 capabilities and
> the Surrogate-Control: header are distinct from the ESI capabilities.
>
> This patch makes Squid always advertise and perform the Surrogate/1.0
> capabilities for reverse-proxy requests.
>
> Full ESI support is no longer required to use the bare-bones
> Surrogate-Control: capabilities.
A quick check though - is it still only enabled for accel ports? (It
shouldn't be enabled for forward proxying).
-Rob
This archive was generated by hypermail 2.2.0 : Wed Feb 10 2010 - 12:00:11 MST