From: Amos Jeffries Date: Mon, 11 Feb 2013 23:34:27 +0000 (-0700) Subject: Release Notes: localip/localport are in 3.3 not 3.2 X-Git-Tag: SQUID_3_4_0_1~287 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7228d3316be1687402ef00b23fd5da326a71f75c;p=thirdparty%2Fsquid.git Release Notes: localip/localport are in 3.3 not 3.2 --- diff --git a/doc/release-notes/release-3.2.sgml b/doc/release-notes/release-3.2.sgml index 79e03d1d8e..8eb9434399 100644 --- a/doc/release-notes/release-3.2.sgml +++ b/doc/release-notes/release-3.2.sgml @@ -595,14 +595,9 @@ This section gives a thorough account of those changes in three categories:

New format referrer to log with the format previously used by referer_log directive.

New format useragent to log with the format previously used by useragent_log directive. - acl : random, localip, localport + acl : random, urllogin

New type random. Pseudo-randomly match requests based on a configured probability. -

Renamed myip to localip. It matches the IP which the client connected to. -

Renamed myport to localport. It matches the port which the client connected to.

Ported urllogin option from Squid 2.7, to match a regex pattern on the URL login field (if any). -

The localip/localport differ from earlier releases where they matched a mix of - of an invalid IP and port 0, the client destination IP/port or the Squid listening IP/port. - This definition is now consistent across all modes of traffic received by Squid.

The manager ACL requires adjustment to cover new cache manager access. So it has now been built-in as a predefined ACL name matching URLs equivalent to the following regular expression: