cvs commit: apache-1.3/htdocs/manual upgrading_to_1_3.html

[marc]

marc        98/10/18 13:08:51

  Modified:    htdocs/manual upgrading_to_1_3.html
  Log:
  While it is fairly obvious that if you upgrade your config files they
  are upgraded, make it explicit.
  
  PR: 3212
  
  Revision  Changes    Path
  1.33      +9 -2      apache-1.3/htdocs/manual/upgrading_to_1_3.html
  
  Index: upgrading_to_1_3.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/upgrading_to_1_3.html,v
  retrieving revision 1.32
  retrieving revision 1.33
  diff -u -r1.32 -r1.33
  --- upgrading_to_1_3.html     1998/09/17 14:52:01     1.32
  +++ upgrading_to_1_3.html     1998/10/18 20:08:51     1.33
  @@ -72,6 +72,13 @@
   <H3>Run-Time Configuration Changes</H3>
   
   <UL>
  +  <LI>There have been numerous changes to the default config files.  
  +    Ensure that you compare your existing configuration files with the
  +    new ones to ensure there aren't any undesired differences.  In
  +    particular, the current config files apply different 
  +    <A HREF="mod/core.html#options">Options</A> and 
  +    <A HREF="mod/core.html#allowoverride">AllowOverride</A> settings to
  +    various directories.
     <LI>As of 1.3.2, <A 
HREF="mod/mod_expires.html"><CODE>mod_expires</CODE></A>
       will add Expires headers to content that does not come from a file 
       on disk, unless you are using a modification time based setting.
  @@ -110,7 +117,7 @@
       "<SAMP>&lt;Limit&nbsp;Get&nbsp;post&gt;</SAMP>" in your configuration
       files, you need to correct them to use uppercase names.
       <P>
  -    Unrecognised method names in the server configuration files will
  +    Unrecognized method names in the server configuration files will
       result in the server logging an error message and failing to start.
       In <SAMP>.htaccess</SAMP> files, unknown methods will cause the
       server to log an error to its error log and return an 'Internal
  @@ -180,7 +187,7 @@
      
     <LI>&lt;Files&gt; sections previously could take a full pathname, and
        were matched against the full pathnames.  This had some
  -     inconsistancies, and was removed.  To emulate this older behaviour
  +     inconsistencies, and was removed.  To emulate this older behaviour
        use a &lt;Files&gt; section nested inside a &lt;Directory&gt;
        section.