Good evening and Happy New Year. Yep, I am home on a New Year's Eve.
I'm watching the C-Band feed of the raw Times Square event from New York.
In any event I am bringing up a new Linux server, replacing the older server
that is running Apache 1.3. The new server is running Fedora Core 6,
updated, so it is running the latest Apache server. I managed to get my
CGI and SSI stuff working again, but the CheckSpelling is not working,
as it currently is on the old server.
I looked for "checkspelling" in the FAQ, but got nothing. Trying to find
something in the previous postings would appear to be a daunting task with
a search capability.
Here are the sections in the config file that contain the directive:
<Directory "/WebDisk/http/htdocs/vidiot">
Options Includes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
CheckSpelling on
</Directory>
<VirtualHost *>
ServerName www.vidiot.com
ServerAlias vidiot.com *.vidiot.com
CheckSpelling on
</VirtualHost>
The Directory section is where it is working in 1.3, but when it didn't
work there, I added it to VirtualHost, as listed in the on line docs.
But it doesn't work there either.
My test is to go to one of my web pages that is upper/lower and then
change one of the uppercase characters to lowercase and look for the page.
I get a page not found. I also did the same thing on the 1.3 server and
it did as I expected, i.e., it found the page and showed the URL with the
correct case.
Thanks in advance for any pointers in figuring out this problem.
MB
--
e-mail: vidiot@xxxxxxxxxx /~\ The ASCII
\ / Ribbon Campaign
[So it's true, scythe matters. Willow 5/12/03] X Against
Visit - URL: http://vidiot.com/ / \ HTML Email
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|