current/doc/source user-manual.sgml,2.205,2.206

Update of /cvsroot/ijbswa/current/doc/source
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv6469/doc/source

Modified Files:
	user-manual.sgml 
Log Message:
Document the CLIENT-TAG pattern


Index: user-manual.sgml
===================================================================
RCS file: /cvsroot/ijbswa/current/doc/source/user-manual.sgml,v
retrieving revision 2.205
retrieving revision 2.206
diff -C2 -d -r2.205 -r2.206
*** user-manual.sgml	17 Mar 2016 10:42:54 -0000	2.205
--- user-manual.sgml	17 Mar 2016 10:43:07 -0000	2.206
***************
*** 2395,2398 ****
--- 2395,2454 ----
  </para>
  
+ <!--   ~~~~~       New section      ~~~~~     -->
+ <sect3 id="client-tag-pattern"><title>The Client Tag Pattern</title>
+ 
+ <!-- XXX: This section contains duplicates content from the
+           client-specific-tag documentation. -->
+ 
+ <warning>
+ <para>
+  This is an experimental feature. The syntax is likely to change in future versions.
+ </para>
+ </warning>
+ 
+ <para>
+  Client tag patterns are not set based on HTTP headers but based on
+  the client's IP address. Users can enable them themselves, but the
+  Privoxy admin controls which tags are available and what their effect
+  is.
+ </para>
+ 
+ <para>
+  After a client-specific tag has been defined with the
+  <link linkend="client-specific-tag">client-specific-tag</link>,
+  directive, action sections can be activated based on the tag by using a
+  CLIENT-TAG pattern. The CLIENT-TAG pattern is evaluated at the same priority
+  as URL patterns, as a result the last matching pattern wins. Tags that
+  are created based on client or server headers are evaluated later on
+  and can overrule CLIENT-TAG and URL patterns!
+ </para>
+ <para>
+  The tag is set for all requests that come from clients that requested
+  it to be set. Note that "clients" are  differentiated by IP address,
+  if the IP address changes the tag has to be requested again.
+ </para>
+ <para>
+  Clients can request tags to be set by using the CGI interface <ulink
+   url="http://config.privoxy.org/show-client-tags">http://config.privoxy.org/show-client-tags</ulink>.
+ </para>
+ 
+ <para>
+  Example:
+ </para>
+ 
+ <para>
+  <screen>
+ # If the admin defined the client-specific-tag circumvent-blocks,
+ # and the request comes from a client that previously requested
+ # the tag to be set, overrule all previous +block actions that
+ # are enabled based on URL to CLIENT-TAG patterns.
+ {-block}
+ CLIENT-TAG:^circumvent-blocks$
+ 
+ # This section is not overruled because it's located after
+ # the previous one.
+ {+block{Nobody is supposed to request this.}}
+ example.org/blocked-example-page</screen>
+ </para>
  
  </sect2>


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140