by Shawn McMaho » Fri, 10 May 1996 04:00:00
Evidently, version 1.03 has a bug; despite my disallowing users to change
their options, the guy had his .htaccess file turning off ExecCGI. I
didn't even think to check that since I had Override turned off.
Oh, well; I didn't really need to prevent them from overriding. Ghu
knows, just letting them have CGIs in the first place is a huge security
breach.
I guess it was assumed, but for a newbie it isn't very obvious.
For apache to be able to read what is in a directory the directory must
have permissions set correctly... double duh....
but no one mentioned that the directory must have all users executable
(the third x in the ls -l command).
Well, again I thank the usenet community for saving me...
cuz i sure didn't find any of this out in a book...
... maybe i'm just blind....
Sent via Deja.com http://www.deja.com/
Before you buy.
3. Apache problem with .htpasswd and REMOTE_USER solved!
5. Newbie solves weird apache problem but wants an explanation
6. ESS1688 (Soundcard) under Linux
7. IIS DoS problems with linux/apache possibly solved
9. Apache + Tomcat + SSL + Warp. Problems Solved
10. Apache 1.2b6: suEXEC - problem solved
11. Apache 1.3.0 VirtualHost problem solved!
12. SOLVED: Java Module problem with Solaris x86/apache 1.2.4
13. Solved Solaris undefined __ucmpdi2 Apache DSO problem