httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_headers.xml
Date Mon, 05 Apr 2004 17:55:58 GMT
nd          2004/04/05 10:55:58

  Modified:    docs/manual/mod mod_headers.xml
  Log:
  document new RequestHeader behaviour
  
  PR: 27951
  Submitted by: vincent gryzor.com (Vincent Deffontaines)
  
  Revision  Changes    Path
  1.12      +11 -1     httpd-2.0/docs/manual/mod/mod_headers.xml
  
  Index: mod_headers.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_headers.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -u -r1.11 -r1.12
  --- mod_headers.xml	2 Apr 2004 21:00:27 -0000	1.11
  +++ mod_headers.xml	5 Apr 2004 17:55:58 -0000	1.12
  @@ -128,7 +128,7 @@
   <name>RequestHeader</name>
   <description>Configure HTTP request headers</description>
   <syntax>RequestHeader set|append|add|unset <var>header</var>
  -[<var>value</var>]</syntax>
  +[<var>value</var> [env=[!]<var>variable</var>]]</syntax>
   <contextlist><context>server config</context><context>virtual host</context>
   <context>directory</context><context>.htaccess</context></contextlist>
   <override>FileInfo</override>
  @@ -170,6 +170,16 @@
       <code>set</code> a <var>value</var> is given as the third argument.
If
       <var>value</var> contains spaces, it should be surrounded by double
       quotes. For unset, no <var>value</var> should be given.</p>
  +
  +    <p>When the <directive>RequestHeader</directive> directive is used
with the
  +    <code>add</code>, <code>append</code>, or <code>set</code>
argument, a
  +    fourth argument may be used to specify conditions under which the action
  +    will be taken. If the <a href="../env.html">environment variable</a>
  +    specified in the <code>env=...</code> argument exists (or if the environment
  +    variable does not exist and <code>env=!...</code> is specified) then the
  +    action specified by the <directive>RequestHeader</directive> directive
will
  +    take effect. Otherwise, the directive will have no effect on the
  +    request.</p>
   
       <p>The <directive>RequestHeader</directive> directive is processed
       just before the request is run by its handler in the fixup phase.
  
  
  

Mime
View raw message