Quote:
Originally Posted by smoker
The easiest way is to add a .htaccess file to the directory concerned containing :
You do not need the + signs in the main config files, which you have included above.
Remember to restart apache after making changes to the main config files. This is not necessary for .htaccess files.
|
Thanks. I forgot to mention that I had tried it in the userdir.conf file with both the + and without the +.
I added an .htaccess file to the directory with the following entry:
I tried it with the + and without the +. It still gives the same error.
There might be something before the configuration gets to the userdir.conf file. I tested other options in the userdir.conf to make changes. Not of them took effect such as turning on Indexes and turning it off.
I also tested to see was the userdir.conf file actually being parsed. I did this by purposely misspelling a word. It's being parsed because the server won't load if the userdir.conf syntax is incorrect.
So, something before or after the loading of the userdir.conf is preventing the userdir.conf configuration from being effective.
Thanks for the time and any other ideas.
By the way, I've being manually configuring web servers for a long time. I'm sure I can eliminate Ubuntu's nice configuration arrangement and make one big httpd.conf file that will work. But I'm trying to take advantage of this intended convenient design.
Edit: By the way, most of the other modules have two files in the mods-available area, a *.conf and a *.load. I have just one perl.load module which I used the a2enmod to enable. Is there a perl.conf file that's missing and possible defaulting to preventing ExecCGI from the /home or the public_html directories?
-- L. James
--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames