marc        97/02/26 18:46:39

  Modified:    htdocs/manual/misc  client_block_api.html
               htdocs/manual/mod  mod_digest.html
  Log:
  Fix typos.
  
  Submitted by: Martin Kraemer <[EMAIL PROTECTED]>
  
  Revision  Changes    Path
  1.4       +2 -2      apache/htdocs/manual/misc/client_block_api.html
  
  Index: client_block_api.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/misc/client_block_api.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -C3 -r1.3 -r1.4
  *** client_block_api.html     1996/11/28 08:34:05     1.3
  --- client_block_api.html     1997/02/27 02:46:37     1.4
  ***************
  *** 38,44 ****
        the module should return that error code. The second parameter
        selects the policy to apply if the request message indicates a
        body, and how a chunked
  !     transfer-coding sho uld be interpreted. Choose one of
    <pre>
        REQUEST_NO_BODY          Send 413 error if message has any body
        REQUEST_CHUNKED_ERROR    Send 411 error if body without Content-Length
  --- 38,44 ----
        the module should return that error code. The second parameter
        selects the policy to apply if the request message indicates a
        body, and how a chunked
  !     transfer-coding should be interpreted. Choose one of
    <pre>
        REQUEST_NO_BODY          Send 413 error if message has any body
        REQUEST_CHUNKED_ERROR    Send 411 error if body without Content-Length
  ***************
  *** 58,64 ****
        should proceed (to step 3).
        This step also sends a 100 Continue response
        to HTTP/1.1 clients, so should not be called until the module
  !     is *defenitely* ready to read content. (otherwise, the point of the
        100 response is defeated). Never call this function more than once.
    
    <li>Finally, call <code>get_client_block</code> in a loop. Pass it a
  --- 58,64 ----
        should proceed (to step 3).
        This step also sends a 100 Continue response
        to HTTP/1.1 clients, so should not be called until the module
  !     is <strong>*definitely*</strong> ready to read content. (otherwise, the 
point of the
        100 response is defeated). Never call this function more than once.
    
    <li>Finally, call <code>get_client_block</code> in a loop. Pass it a
  
  
  
  1.4       +2 -2      apache/htdocs/manual/mod/mod_digest.html
  
  Index: mod_digest.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_digest.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -C3 -r1.3 -r1.4
  *** mod_digest.html   1996/12/02 18:14:04     1.3
  --- mod_digest.html   1997/02/27 02:46:38     1.4
  ***************
  *** 42,54 ****
    
    <p>Using MD5 Digest authentication is very simple. Simply set up
    authentication normally. However, use "AuthType Digest" and
  ! "AuthDigestFIle" instead of the normal "AuthType Basic" and
    "AuthUserFile". Everything else should remain the same.</p>
    
    <p>MD5 authentication provides a more secure password system, but only
    works with supporting browsers. As of this writing (July 1996), the
    majority of browsers do not support digest authentication. Therefore, we
  ! do not reccomend using this feature on a large Internet site. However, for
    personal and intra-net use, where browser users can be controlled, it is
    ideal.</p>
    
  --- 42,54 ----
    
    <p>Using MD5 Digest authentication is very simple. Simply set up
    authentication normally. However, use "AuthType Digest" and
  ! "AuthDigestFile" instead of the normal "AuthType Basic" and
    "AuthUserFile". Everything else should remain the same.</p>
    
    <p>MD5 authentication provides a more secure password system, but only
    works with supporting browsers. As of this writing (July 1996), the
    majority of browsers do not support digest authentication. Therefore, we
  ! do not recommend using this feature on a large Internet site. However, for
    personal and intra-net use, where browser users can be controlled, it is
    ideal.</p>
    
  
  
  

Reply via email to