httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Pepper <>
Subject [PATCH] httpd-docs-1.3/htdocs/manual/howto/cgi.html
Date Thu, 16 Nov 2000 20:58:05 GMT
   Modified: httpd-docs-1.3/htdocs/manual/howto/cgi.html
   Removed spaces and slashes from internal fragment names and hrefs. 
Fixed a couple closing tags.
   Note: This one should be complete; previous patches had '-w' as an 
option to cvs diff, skipping most of the changes. --cp

Index: cgi.html
RCS file: /home/cvspublic/httpd-docs-1.3/htdocs/manual/howto/cgi.html,v
retrieving revision 1.4
diff -u -d -b -r1.4 cgi.html
--- cgi.html	2000/11/12 23:54:17	1.4
+++ cgi.html	2000/11/16 20:58:11
@@ -14,68 +14,68 @@

-<li><a href="#dynamic content with cgi">Dynamic Content with
+<li><a href="#dynamiccontentwithcgi">Dynamic Content with

-<li><a href="#configuring apache to permit cgi">Configuring Apache to
+<li><a href="#configuringapachetopermitcgi">Configuring Apache to
  permit CGI</a>

  <li><a href="#scriptalias">ScriptAlias</a></li>

-<li><a href="#cgi outside of scriptalias directories">CGI outside of
+<li><a href="#cgioutsideofscriptaliasdirectories">CGI outside of
  ScriptAlias directories</a>

  <li><a href=
-"#explicitly using options to permit cgi execution">Explicitly using
+"#explicitlyusingoptionstopermitcgiexecution">Explicitly using
  Options to permit CGI execution</a></li>

-<li><a href="#.htaccess files">.htaccess files</a></li>
+<li><a href="#.htaccessfiles">.htaccess files</a></li>

-<li><a href="#writing a cgi script">Writing a CGI script</a>
+<li><a href="#writingacgiscript">Writing a CGI script</a>

-<li><a href="#your first cgi script">Your first CGI script</a></li>
+<li><a href="#yourfirstcgiscript">Your first CGI script</a></li>

-<li><a href="#but it's still not working!">But it's still not
+<li><a href="#butit'sstillnotworking!">But it's still not

-<li><a href="#file permissions">File permissions</a></li>
+<li><a href="#filepermissions">File permissions</a></li>

-<li><a href="#path information">Path information</a></li>
+<li><a href="#pathinformation">Path information</a></li>

-<li><a href="#syntax errors">Syntax errors</a></li>
+<li><a href="#syntaxerrors">Syntax errors</a></li>

-<li><a href="#error logs">Error logs</a></li>
+<li><a href="#errorlogs">Error logs</a></li>

-<li><a href="#what's going on behind the scenes">What's going on behind
+<li><a href="#what'sgoingonbehindthescenes">What's going on behind
  the scenes?</a>

-<li><a href="#environment variables">Environment variables</a></li>
+<li><a href="#environmentvariables">Environment variables</a></li>

-<li><a href="#stdin and stdout">STDIN and STDOUT</a></li>
+<li><a href="#stdinandstdout">STDIN and STDOUT</a></li>

-<li><a href="#cgi modules/libraries">CGI modules/libraries</a></li>
+<li><a href="#cgimoduleslibraries">CGI modules/libraries</a></li>

-<li><a href="#for more information">For more information</a></li>
+<li><a href="#formoreinformation">For more information</a></li>

  <!-- INDEX END -->
-<h2><a name="dynamic content with cgi">Dynamic Content with
+<h2><a name="dynamiccontentwithcgi">Dynamic Content with

  <table border="1">
@@ -101,7 +101,7 @@
  Apache web server, and getting started writing CGI scripts.</p>

-<h2><a name="configuring apache to permit cgi">Configuring Apache to
+<h2><a name="configuringapachetopermitcgi">Configuring Apache to
  permit CGI</a></h2>

  <p>In order to get your CGI scripts to work properly, you'll need to
@@ -143,7 +143,7 @@
  Of course, the file will have to exist, and be executable, and return
  output in a particular way, or Apache will return an error message.</p>

-<h3><a name="cgi outside of scriptalias directories">CGI outside of
+<h3><a name="cgioutsideofscriptaliasdirectories">CGI outside of
  ScriptAlias directories</a></h3>

  <p>CGI scripts are often restricted to <code>ScriptAlias</code>'ed
@@ -158,7 +158,7 @@
  scripts elsewhere.</p>

  <h3><a name=
-"explicitly using options to permit cgi execution">Explicitly using
+"explicitlyusingoptionstopermitcgiexecution">Explicitly using
  Options to permit CGI execution</a></h3>

  <p>You could explicitly use the <code>Options</code> directive, inside
@@ -181,7 +181,7 @@
       AddHandler cgi-script cgi pl

-<h3><a name=".htaccess files">.htaccess files</a></h3>
+<h3><a name=".htaccessfiles">.htaccess files</a></h3>

  <p>A <code>.htaccess</code> file is a way to set configuration
  directives on a per-directory basis. When Apache serves a resource, it
@@ -209,7 +209,7 @@
  this directory.</p>

-<h2><a name="writing a cgi script">Writing a CGI script</a></h2>
+<h2><a name="writingacgiscript">Writing a CGI script</a></h2>

  <p>There are two main differences between ``regular'' programming, and
  CGI programming.</p>
@@ -230,7 +230,7 @@
  <p>Apart from those two things, writing a CGI script will look a lot
  like any other program that you might write.</p>

-<h3><a name="your first cgi script">Your first CGI script</a></h3>
+<h3><a name="yourfirstcgiscript">Your first CGI script</a></h3>

  <p>The following is an example CGI script that prints one line to your
  browser. Type in the following, save it to a file called
@@ -256,7 +256,7 @@
  <p>If you open your favorite browser and tell it to get the address</p>


  <p>or wherever you put your file, you will see the one line
@@ -265,7 +265,7 @@
  getting just about anything working.</p>

-<h2><a name="but it's still not working!">But it's still not
+<h2><a name="butit'sstillnotworking!">But it's still not

  <p>There are four basic things that you may see in your browser when
@@ -278,24 +278,24 @@
  <dt>The source code of your CGI script</dt>
  <dd>That means that you have not properly configured Apache to process
  your CGI script.  Reread the section on <a
  Apache</a> and try to find what you missed.<br><br></dd>

  <dt>A message starting with "Forbidden"</dt> <dd>That means that there
-is a permissions problem.  Check the <a href="#error%20logs">Apache
+is a permissions problem.  Check the <a href="#errorlogs">Apache
  error log</a> and the section below on <a
-href="#file%20permissions">file permissions</a>.<br><br></dd>
+href="#filepermissions">file permissions</a>.<br><br></dd>

  <dt>A message saying "Internal Server Error"</dt> <dd>If you check the
-<a href="#error%20logs">Apache error log</a>, you will probably find
+<a href="#errorlogs">Apache error log</a>, you will probably find
  that it says "Premature end of script headers", possibly along with an
  error message generated by your CGI script.  In this case, you will
  want to check each of the below sections to see what might be preventing
-your CGI script from emitting the proper HTTP headers.</dt>
+your CGI script from emitting the proper HTTP headers.</dd>

-<h3><a name="file permissions">File permissions</a></h3>
+<h3><a name="filepermissions">File permissions</a></h3>

  <p>Remember that the server does not run as you. That is, when the
  server starts up, it is running with the permissions of an unprivileged
@@ -321,7 +321,7 @@
  In this case, you will need to check the suexec log file to see what
  specific security check is failing.</p>

-<h3><a name="path information">Path information</a></h3>
+<h3><a name="pathinformation">Path information</a></h3>

  <p>When you run a program from your command line, you have certain
  information that is passed to the shell without you thinking about it.
@@ -344,7 +344,7 @@

  <p>Make sure that this is in fact the path to the interpreter.</p>

-<h3><a name="syntax errors">Syntax errors</a></h3>
+<h3><a name="syntaxerrors">Syntax errors</a></h3>

  <p>Most of the time when a CGI script fails, it's because of a problem
  with the script itself. This is particularly true once you get the
@@ -352,7 +352,7 @@
  Always attempt to run your script from the command line before you
  test if via a browser. This will eliminate most of your problems.</p>

-<h3><a name="error logs">Error logs</a></h3>
+<h3><a name="errorlogs">Error logs</a></h3>

  <p>The error logs are your friend. Anything that goes wrong generates
  message in the error log. You should always look there first. If the
@@ -362,7 +362,7 @@
  problems are quickly identified, and quickly solved.</p>

-<h2><a name="what's going on behind the scenes">What's going on behind
+<h2><a name="what'sgoingonbehindthescenes">What's going on behind
  the scenes?</a></h2>

  <p>As you become more advanced in CGI programming, it will become
@@ -371,7 +371,7 @@
  Because although it's all very well to write a script that prints
  ``Hello, World.'', it's not particularly useful.</p>

-<h3><a name="environment variables">Environment variables</a></h3>
+<h3><a name="environmentvariables">Environment variables</a></h3>

  <p>Environment variables are values that float around you as you use
  your computer. They are useful things like your path (where the
@@ -408,7 +408,7 @@

-<h3><a name="stdin and stdout">STDIN and STDOUT</a></h3>
+<h3><a name="stdinandstdout">STDIN and STDOUT</a></h3>

  <p>Other communication between the server and the client happens over
  standard input (<code>STDIN</code>) and standard output
@@ -447,7 +447,7 @@
  aspects of your CGI script.</p>

-<h2><a name="cgi modules/libraries">CGI modules/libraries</a></h2>
+<h2><a name="cgimoduleslibraries">CGI modules/libraries</a></h2>

  <p>When you write CGI scripts, you should consider using a code
  library, or module, to do most of the grunt work for you. This leads to
@@ -464,7 +464,7 @@

-<h2><a name="for more information">For more information</a></h2>
+<h2><a name="formoreinformation">For more information</a></h2>

  <p>There are a large number of CGI resources on the web. You can
  discuss CGI problems with other users on the Usenet group

View raw message