httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-2.0/docs/manual/mod mod_unique_id.html
Date Thu, 07 Jun 2001 05:12:23 GMT
yoshiki     01/06/06 22:12:23

  Modified:    docs/manual/mod mod_unique_id.html
  Port typo fix from 1.3.
  Revision  Changes    Path
  1.6       +2 -2      httpd-2.0/docs/manual/mod/mod_unique_id.html
  Index: mod_unique_id.html
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_unique_id.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- mod_unique_id.html	2000/09/28 16:55:51	1.5
  +++ mod_unique_id.html	2001/06/07 05:12:22	1.6
  @@ -138,7 +138,7 @@
   repeated itself).  This is not a perfect defense.
  -How good a defense is it?  Well suppose that one of your machines serves
  +How good a defense is it?  We'll suppose that one of your machines serves
   at most 500 requests per second (which is a very reasonable upper bound
   at this writing, because systems generally do more than just shovel out
   static files).  To do that it will require a number of children which
  @@ -164,7 +164,7 @@
   The <CODE>UNIQUE_ID</CODE> environment variable is constructed by
   encoding the 112-bit (32-bit IP address, 32 bit pid, 32 bit time stamp,
  -16 bit counter) quadruple using the alphabet <CODE>[A-Za-z0-9@-]</CODE>
  +16 bit counter quadruple) using the alphabet <CODE>[A-Za-z0-9@-]</CODE>
   in a manner similar to MIME base64 encoding, producing 19 characters.
   The MIME base64 alphabet is actually <CODE>[A-Za-z0-9+/]</CODE> however
   <CODE>+</CODE> and <CODE>/</CODE> need to be specially encoded
in URLs,

View raw message