From: Amos Jeffries <squid3@treenet.co.nz>
Date: Mon, 9 Dec 2013 01:11:47 +0000 (-0700)
Subject: Release notes: spotlight key_extras feature
X-Git-Tag: SQUID_3_5_0_1~470
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4e022adfca1a628f2d15c0ab413168e422891bc2;p=thirdparty%2Fsquid.git

Release notes: spotlight key_extras feature
---

diff --git a/doc/release-notes/release-3.5.sgml b/doc/release-notes/release-3.5.sgml
index d1837d4660..f8dbc8fde3 100644
--- a/doc/release-notes/release-3.5.sgml
+++ b/doc/release-notes/release-3.5.sgml
@@ -39,6 +39,7 @@ The 3.5 change history can be <url url="http://www.squid-cache.org/Versions/v3/3
 <p>The most important of these new features are:
 <itemize>
 	<item>Support libecap v1.0
+	<item>Authentication helper query extensions
 </itemize>
 
 Most user-facing changes are reflected in squid.conf (see below).
@@ -56,6 +57,20 @@ Most user-facing changes are reflected in squid.conf (see below).
    due to API changes.
 
 
+<sect1>Authentication helper query extensions
+<p>Details at <url url="http://www.squid-cache.org/Doc/config/auth_param/">.
+
+<p>The new <em>key_extras</em> parameter allows sending of additional
+  details to the authentication helper beyond the minimum required for
+  the HTTP authentication. This is primarily intended to allow switching
+  of authentication databases based on criteria such as client IP subnet,
+  Squid receiving port, or in reverse-proxy the requested domain name.
+
+<p>In theory any <em>logformat</em> code may be used, however only the
+  codes which have available details at the time of authentication
+  will send any meaningful detail.
+
+
 <sect>Changes to squid.conf since Squid-3.4
 <p>
 There have been changes to Squid's configuration file since Squid-3.4.