First, the question. Is the documentation supposed to reflect the actual
function of the code, or is it more of a recommendation? The reason that
I ask this is that /htdocs/manual/windows.html states the following:
However, because Apache uses Unix-style names internally, you must use
forward slashes, not backslashes.
This is not actually true. You can use whatever slashes make you happy.
You can even mix them, if you're careful. I had changed this, but then
changed it back, because I was not sure if this was actually intended to
be more of a suggestion. "You really aught to ..." I've found, in
teaching Perl to Windows people, that the simple notion of using /
instead of \ really confuses folks. Particularly when \n somewhere in a
file path does something rather unexpected.
Anyways, here's a patch. I submitted something somewhat like this
earlier, but it was against the old 1.3 stuff, not the new-and-improved
2.0 document.
<PATCH>
--- ../apache-2.0/htdocs/manual/windows.html Wed Mar 22 16:05:25 2000
+++ ./windows.html Sun Mar 26 21:27:38 2000
@@ -35,7 +35,7 @@
<LI><A HREF="#down">Downloading Apache for Windows</A>
<LI><A HREF="#inst">Installing Apache for Windows (binary
install)</A>
<LI><A HREF="#run">Running Apache for Windows</A>
- <LI><A HREF="#use">Using Apache for Windows</A>
+ <LI><A HREF="#config">Configuring Apache for Windows</A>
<LI><A HREF="#cmdline">Running Apache for Windows from the Command
Line</A>
<LI><A HREF="#service">Running Apache for Windows as a Service</A>
<LI><A HREF="#signal">Signalling Console Apache when running</A>
@@ -118,7 +118,7 @@
Also, if you already have a file called <SAMP>htdocs\index.html</SAMP>
then it will not be overwritten (no <SAMP>index.html.default</SAMP>
-file will be installed either). This should mean it a safe to install
+file will be installed either). This should mean it is safe to install
Apache over an existing installation (but you will have to stop the
existing server running before doing the installation, then start the
new one after the installation is finished).
@@ -144,7 +144,7 @@
<LI>From a <A HREF="#cmdline">console window</A>. This is the only
option
available for
- Windows 95 users.
+ Windows 95 and Windows 98 users.
</UL>
To start Apache as a service, you first need to install it as a
@@ -205,7 +205,7 @@
Once your basic installation is working, you should configure it
properly by editing the files in the <SAMP>conf</SAMP> directory.
-<H2><A NAME="use">Configuring Apache for Windows</A></H2>
+<H2><A NAME="config">Configuring Apache for Windows</A></H2>
Apache is configured by files in the <SAMP>conf</SAMP>
directory. These are the same as files used to configure the Unix
@@ -249,7 +249,13 @@
Windows filenames instead of Unix ones. However, because Apache
uses Unix-style names internally, you must use forward slashes,
not
backslashes. Drive letters can be used; if omitted, the drive
with
- the Apache executable will be assumed.</P>
+ the Apache executable will be assumed. If you use file names, or
+ directory names, containing spaces, you need to enclose the file
+ path and name in quotes:</P>
+<PRE>
+ ServerRoot "c:/Program Files/Apache Group/Apache"
+</PRe>
+
<LI><P>Apache for Windows contains the ability to load modules at
runtime,
without recompiling the server. If Apache is compiled normally,
it
will install a number of optional modules in the
</PATCH>
--
http://www.ApacheUnleashed.com/
Lexington Perl Mongers - http://lexington.pm.org/
PGP Key - http://www.rcbowen.com/pgp.txt
