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

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

Modified Files:
	user-manual.sgml 
Log Message:
Start referring to tags that are created based on HTTP headers as request tags

... to reduce confusion now that we also have client-specific tags.


Index: user-manual.sgml
===================================================================
RCS file: /cvsroot/ijbswa/current/doc/source/user-manual.sgml,v
retrieving revision 2.204
retrieving revision 2.205
diff -C2 -d -r2.204 -r2.205
*** user-manual.sgml	4 Mar 2016 13:21:54 -0000	2.204
--- user-manual.sgml	17 Mar 2016 10:42:54 -0000	2.205
***************
*** 2320,2335 ****
  
  <!--   ~~~~~       New section      ~~~~~     -->
! <sect3 id="tag-pattern"><title>The Tag Pattern</title>
  
  <para>
!  Tag patterns are used to change the applying actions based on the
!  request's tags. Tags can be created with either the
!  <link linkend="CLIENT-HEADER-TAGGER">client-header-tagger</link>
   or the  <link linkend="SERVER-HEADER-TAGGER">server-header-tagger</link> action.
  </para>
  
  <para>
!  Tag patterns have to start with <quote>TAG:</quote>, so &my-app;
!  can tell them apart from URL patterns. Everything after the colon
   including white space, is interpreted as a regular expression with
   path pattern syntax, except that tag patterns aren't left-anchored
--- 2320,2335 ----
  
  <!--   ~~~~~       New section      ~~~~~     -->
! <sect3 id="tag-pattern"><title>The Request Tag Pattern</title>
  
  <para>
!  Request tag patterns are used to change the applying actions based on the
!  request's tags. Tags can be created based on HTTP headers with either
!  the <link linkend="CLIENT-HEADER-TAGGER">client-header-tagger</link>
   or the  <link linkend="SERVER-HEADER-TAGGER">server-header-tagger</link> action.
  </para>
  
  <para>
!  Request tag patterns have to start with <quote>TAG:</quote>, so &my-app;
!  can tell them apart from other patterns. Everything after the colon
   including white space, is interpreted as a regular expression with
   path pattern syntax, except that tag patterns aren't left-anchored
***************
*** 2347,2359 ****
  
  <para>
!  Sections can contain URL and tag patterns at the same time,
!  but tag patterns are checked after the URL patterns and thus
   always overrule them, even if they are located before the URL patterns.
  </para>
  
  <para>
!  Once a new tag is added, Privoxy checks right away if it's matched by one
!  of the tag patterns and updates the action settings accordingly. As a result
!  tags can be used to activate other tagger actions, as long as these other
   taggers look for headers that haven't already be parsed.
  </para>
--- 2347,2359 ----
  
  <para>
!  Sections can contain URL and request tag patterns at the same time,
!  but request tag patterns are checked after the URL patterns and thus
   always overrule them, even if they are located before the URL patterns.
  </para>
  
  <para>
!  Once a new request tag is added, Privoxy checks right away if it's matched by one
!  of the request tag patterns and updates the action settings accordingly. As a result
!  request tags can be used to activate other tagger actions, as long as these other
   taggers look for headers that haven't already be parsed.
  </para>
***************
*** 2380,2387 ****
  
  <!--   ~~~~~       New section      ~~~~~     -->
! <sect3 id="negative-tag-patterns"><title>The Negative Tag Patterns</title>
  
  <para>
!  To match requests that do not have a certain tag, specify a negative tag pattern
   by prefixing the tag pattern line with either <quote>NO-REQUEST-TAG:</quote>
   or <quote>NO-RESPONSE-TAG:</quote> instead of <quote>TAG:</quote>.
--- 2380,2387 ----
  
  <!--   ~~~~~       New section      ~~~~~     -->
! <sect3 id="negative-tag-patterns"><title>The Negative Request Tag Patterns</title>
  
  <para>
!  To match requests that do not have a certain request tag, specify a negative tag pattern
   by prefixing the tag pattern line with either <quote>NO-REQUEST-TAG:</quote>
   or <quote>NO-RESPONSE-TAG:</quote> instead of <quote>TAG:</quote>.
***************
*** 2389,2393 ****
  
  <para>
!  Negative tag patterns created with <quote>NO-REQUEST-TAG:</quote> are checked
   after all client headers are scanned, the ones created with <quote>NO-RESPONSE-TAG:</quote>
   are checked after all server headers are scanned. In both cases all the created
--- 2389,2393 ----
  
  <para>
!  Negative request tag patterns created with <quote>NO-REQUEST-TAG:</quote> are checked
   after all client headers are scanned, the ones created with <quote>NO-RESPONSE-TAG:</quote>
   are checked after all server headers are scanned. In both cases all the created


------------------------------------------------------------------------------
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