httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mar...@apache.org
Subject cvs commit: apache-1.3/src/modules/experimental mod_auth_digest.c
Date Wed, 07 Feb 2001 23:43:54 GMT
martin      01/02/07 15:43:52

  Modified:    src      CHANGES
               src/modules/experimental mod_auth_digest.c
  Log:
  Fix spelling of "referrer"
  Submitted by:	"Todd T. Fries" <todd@fries.net>
  
  Revision  Changes    Path
  1.1638    +1 -1      apache-1.3/src/CHANGES
  
  Index: CHANGES
  ===================================================================
  RCS file: /home/cvs/apache-1.3/src/CHANGES,v
  retrieving revision 1.1637
  retrieving revision 1.1638
  diff -u -u -r1.1637 -r1.1638
  --- CHANGES	2001/02/01 13:07:19	1.1637
  +++ CHANGES	2001/02/07 23:43:44	1.1638
  @@ -2926,7 +2926,7 @@
   
     *) Cache a proxied request in the event that the client cancels the
        transfer, provided that the configured percentage of the file has
  -     already been transfered. It works for HTTP transfers only.  The 
  +     already been transferred. It works for HTTP transfers only.  The 
        new configuration directive is called CacheForceCompletion. 
        [Glen Parker <glenebob@nwlink.com>] PR#2277
   
  
  
  
  1.22      +1 -1      apache-1.3/src/modules/experimental/mod_auth_digest.c
  
  Index: mod_auth_digest.c
  ===================================================================
  RCS file: /home/cvs/apache-1.3/src/modules/experimental/mod_auth_digest.c,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -u -r1.21 -r1.22
  --- mod_auth_digest.c	2001/01/15 17:05:23	1.21
  +++ mod_auth_digest.c	2001/02/07 23:43:50	1.22
  @@ -651,7 +651,7 @@
   /*
    * client list code
    *
  - * Each client is assigned a number, which is transfered in the opaque
  + * Each client is assigned a number, which is transferred in the opaque
    * field of the WWW-Authenticate and Authorization headers. The number
    * is just a simple counter which is incremented for each new client.
    * Clients can't forge this number because it is hashed up into the
  
  
  

Mime
View raw message