Using .htaccess Files with Apache Page 6
.htaccessare the performance impact and the extending of control access to others. The first is somewhat manageable through the judicious use of the
AllowOverridedirective, and the latter is a matter of establishing trust -- and performing risk assessment. What mix works best in your environment is something you'll need to determine for yourself.
Here are some of the most common problems I've seen people have
(or have had myself) with
.htaccess files. One thing I
should stress first, though: the server error log is your friend.
You should always consult the error log when things don't seem to
be functioning correctly. If it doesn't say anything about your
problem, try boosting the message detail by changing your
LogLevel directive to
LogLevel debug line of you don't have
- 'Internal Server Error' page is displayed when a document is requested
- This indicates a problem with your configuration. Check the
Apache error log file for a more detailed explanation of what
went wrong. You probably have used a directive that isn't allowed
.htaccessfiles, or have a directive with incorrect syntax.
.htaccessfile doesn't seem to change anything
- It's possible that the directory is within the scope of an
AllowOverride Nonedirective. Try putting a line of gibberish in the
.htaccessfile and force a reload of the page. If you still get the same page instead of an 'Internal Server Error' display, then this is probably the cause of the problem. Another slight possibility is that the document you're requesting isn't actually controlled by the
.htaccessfile you're editing; this can sometimes happen if you're accessing a document with a common name, such as
index.html. If there's any chance of this, try changing the actual document and requesting it again to make sure you can see the change. this isn't happening.
- I've added some security directives to my
.htaccessfile, but I'm not getting challenged for a username and password
- The most common cause of this is having the
.htaccessdirectives within the scope of a
Satisfy Anydirective. Explicitly disable this by adding a
Satisfy Allto the
.htaccessfile, and try again.
Once you've got your Apache Web server up and running, the first hurdle has been surmounted. Now you can move on to exploring its capabilities and features. Here are some pointers to resources for further investigation:
- The main Apache Web site, of course: <URL:http://www.apache.org/>
- The documentation for Apache and its modules: <URL:http://www.apache.org/docs/>
The canonical email response page:
(This page is normally used to respond to email requests for support, but there are lots of good resources listed on it.)
IT Solutions Builder TOP IT RESOURCES TO MOVE YOUR BUSINESS FORWARD
Which topic are you interested in?
What is your company size?
What is your job title?
What is your job function?
Searching our resource database to find your matches...