httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stodd...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_headers.html
Date Fri, 01 Jun 2001 04:39:10 GMT
stoddard    01/05/31 21:39:09

  Modified:    .        CHANGES
               docs/manual/mod mod_headers.html
  Log:
  Update doc with info on Header echo directive
  
  Revision  Changes    Path
  1.210     +4 -0      httpd-2.0/CHANGES
  
  Index: CHANGES
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/CHANGES,v
  retrieving revision 1.209
  retrieving revision 1.210
  diff -u -r1.209 -r1.210
  --- CHANGES	2001/05/23 13:56:31	1.209
  +++ CHANGES	2001/06/01 04:39:06	1.210
  @@ -1,4 +1,8 @@
   Changes with Apache 2.0.19-dev
  +  *) New Header directive 'echo' option. "Header echo regex" will
  +     cause any headers received on the request that match regex to be
  +     echoed to (included in) the response headers.
  +     [Bill Stoddard]
   
     *) include/ap_compat.h tested and set APR_COMPAT_H instead of AP_COMPAT_H.
        This prevented the inclusion of apr_compat.h.  PR #7773
  
  
  
  1.17      +19 -6     httpd-2.0/docs/manual/mod/mod_headers.html
  
  Index: mod_headers.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_headers.html,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- mod_headers.html	2001/05/30 08:35:33	1.16
  +++ mod_headers.html	2001/06/01 04:39:08	1.17
  @@ -158,6 +158,10 @@
    REL="Help"
   ><STRONG>Syntax:</STRONG></A> Header unset <EM>header</EM><BR>
   <A
  + HREF="directive-dict.html#Syntax"
  + REL="Help"
  +><STRONG>Syntax:</STRONG></A> Header echo <EM>header</EM><BR>
  +<A
    HREF="directive-dict.html#Context"
    REL="Help"
   ><STRONG>Context:</STRONG></A> server config, virtual host, access.conf,
  @@ -178,8 +182,7 @@
   This directive can replace, merge or remove HTTP response headers. The header
   is modified just after the content handler and output filters are run, 
   allowing outgoing headers to be modified. The action it performs is determined 
  -by the first argument. This can be one of the following values, as with
  -RequestHeader:
  +by the first argument. This can be one of the following values:
   
   <UL>
   <LI><STRONG>set</STRONG><BR>
  @@ -200,13 +203,23 @@
   <LI><STRONG>unset</STRONG><BR>
     The response header of this name is removed, if it exists. If there are
     multiple headers of the same name, all will be removed.
  +
  +<LI><STRONG>echo</STRONG><BR>
  +  Request headers with this name are echoed back in the response headers.
  +  <EM>header</EM> may be a regular expression. For example, the directive
  +  <P>
  +  Header echo ^TS*
  +  <P>
  +  will cause all request headers that begin with TS to be echoed
  +  or copied over to the response headers.
   </UL>
   
   This argument is followed by a header name, which can include the
  -final colon, but it is not required. Case is ignored. For
  -add, append and set a value is given as the third argument. If this
  -value contains spaces, it should be surrounded by double quotes.
  -For unset, no value should be given.
  +final colon, but it is not required. Case is ignored for set, append, add
  +and unset. The header name for echo is case sensitive and may be a
  +regular expression. For add, append and set a value is given as the third 
  +argument. If this value contains spaces, it should be surrounded by double 
  +quotes. For unset and echo, no value should be given.
   
   <H3>Order of Processing</H3>
   
  
  
  

Mime
View raw message