From: Joshua Slive Date: Mon, 6 Nov 2000 22:47:06 +0000 (+0000) Subject: Grammar/Style fixes. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=23f55ae6e4df29a70d3f0bfa665d03fe61eb61b2;p=apache Grammar/Style fixes. Submitted by: Chris Pepper git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@86850 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/compat_notes.html b/docs/manual/misc/compat_notes.html index 719ee93ea9..a8301b68e3 100644 --- a/docs/manual/misc/compat_notes.html +++ b/docs/manual/misc/compat_notes.html @@ -22,7 +22,7 @@ httpd, there are a couple gotcha's to watch out for. These are mostly due to the fact that the parser for config and access control files was rewritten from scratch, so certain liberties the earlier servers took may not be available here. These are all easily fixable. If you -know of other non-fatal problems that belong here, let us know.

Please also check the known @@ -43,7 +43,7 @@ client problems page.

  • If you follow the NCSA guidelines for setting up access restrictions based on client domain, you may well have added - entries for, AuthType, AuthName, AuthUserFile or + entries for AuthType, AuthName, AuthUserFile or AuthGroupFile. None of these are needed (or appropriate) for restricting access based on client domain. When Apache sees AuthType it (reasonably) @@ -57,7 +57,7 @@ client problems page.

  • exec cgi="" produces reasonable malformed header responses when used to invoke non-CGI scripts.
    - The NCSA code ignores the missing header. (bad idea) + The NCSA code ignores the missing header (bad idea).
    Solution: write CGI to the CGI spec and use include virtual, or use exec cmd="" instead. @@ -90,7 +90,7 @@ client problems page. booting unless an added optional keyword is included.

    -

  • Apache does not implement OnDeny use +
  • Apache does not implement OnDeny; use ErrorDocument instead. @@ -115,7 +115,7 @@ client problems page.
  • Apache does not allow ServerRoot settings inside a VirtualHost container. There is only one global ServerRoot in Apache; any desired changes in paths for virtual hosts need to be made with the explicit - directives, eg. DocumentRoot, TransferLog, etc. + directives, e.g., DocumentRoot, TransferLog, etc. diff --git a/docs/manual/misc/howto.html b/docs/manual/misc/howto.html index 9ce92a41ba..57c9f2dfa8 100644 --- a/docs/manual/misc/howto.html +++ b/docs/manual/misc/howto.html @@ -57,11 +57,11 @@ If that module is compiled in, the following lines RewriteRule /.* http://www.apache.org/ [R] -This will send an HTTP 302 Redirect back to the client, and no matter +will send an HTTP 302 Redirect back to the client, and no matter what they gave in the original URL, they'll be sent to -"http://www.apache.org". +"http://www.apache.org/". -The second option is to set up a ScriptAlias pointing to +

    The second option is to set up a ScriptAlias pointing to a CGI script which outputs a 301 or 302 status and the location of the other server.

    @@ -89,7 +89,7 @@ print "Status: 302 Moved Temporarily\r\n" . "Location: http://www.some.where.else.com/\r\n" . "\r\n"; -

    +
    @@ -118,7 +118,6 @@ it to reopen the logfiles.

    mv access_log access_log.old
    kill -1 `cat httpd.pid` -

    Note: httpd.pid is a file containing the process id @@ -135,7 +134,7 @@ nightly or weekly basis.

    robots.txt which you don't have, and never did have?

    These clients are called robots (also known as crawlers, -spiders and other cute name) - special automated clients which +spiders and other cute names) - special automated clients which wander around the web looking for interesting resources.

    Most robots are used to generate some kind of web index which @@ -155,7 +154,7 @@ will want to stop.

    Another reason some webmasters want to block access to robots, is to stop them indexing dynamic information. Many search engines will use the -data collected from your pages for months to come - not much use if your +data collected from your pages for months to come - not much use if you're serving stock quotes, news, weather reports or anything else that will be stale by the time people find it in a search engine.

    @@ -194,7 +193,7 @@ to set the directive ProxyRemote differently. Here are my settings:

    Requests on port 80 of my proxy nicklas are forwarded to -proxy.mayn.franken.de:8080, while requests on port 443 are +proxy.mayn.franken.de:8080, while requests on port 443 are forwarded to proxy.mayn.franken.de:443. If the remote proxy is not set up to handle port 443, then the last directive can be left out. SSL requests