CentOS. htaccess solutions that don't work _linux

Results click a link directly 404 Not Found. Tragedy, it seems that the Apache rewrite part of the problem, completely ignored. htaccess file! After checking the Apache module, found that the rewrite module is open, it appears that the configuration of the httpd.conf file is a bit problematic. Recall that prior to configuring rewrite under Ubuntu server is also enabled a allowoverride called "all" to correctly open the rewrite, this time the manual configuration VirtualHost did not write these two sentences, That seems to be the problem.

Immediately enter:

#vim/etc/httpd/conf/httpd.conf
Find your own VirtualHost settings section, add on

<directory/>
AllowOverride All
</Directory>
The above Directory/"/" for your WWW path, such as placed under the "/var/www/html" path is written as "<Directory/var/www/html>", and so on. Restart the httpd service after saving:

#/etc/init.d/httpd restart
Enter WordPress again, click on a link, became! Solve the problem. It seems that the "allowoverride" is not simple ah! So I went online to find a lap and found this to be the key point of control. htaccess. In addition to the need to open rewrite in Apache, and the correct setting of the. htaccess file name, you also need to configure the allowoverride of the directory, because by default the allowoverride value is none, which completely ignores the. htaccess file.

In addition, AllowOverride has a number of values in addition to all and none, and their meanings are as follows:

Authconfig
Allow the use of instructions related to the authentication authorization (authdbmgroupfile, Authdbmuserfile, AuthGroupFile, AuthName, AuthType, AuthUserFile, Require, etc.).

FileInfo
Instructions for using control document types are allowed (DefaultType, ErrorDocument, Forcetype, languagepriority, SetHandler, Setinputfilter, Setoutputfilter, Mod_mime add* and remove* directives, etc.), instructions for controlling document metadata (Header, Requestheader, Setenvif, Setenvifnocase, Browsermatch, Cookieexpires , Cookiedomain, Cookiestyle, cookietracking, cookiename), mod_rewrite instructions (rewriteengine, rewriteoptions, RewriteBase, Rewritecond, Rewriterule) and the action instruction in mod_actions.

Indexes
Permission to use commands that control the index of the directory (Adddescription, AddIcon, addiconbyencoding, Addiconbytype, DefaultIcon, DirectoryIndex, FancyIndexing, Headername, Indexignore, indexoptions, Readmename, etc.).

Limit
Allows commands to be accessed using the control host (Allow, Deny, order).

Options[=option,...]
Allows you to use instructions that control the specified directory functionality (options and Xbithack). You can attach a comma-delimited (space-free) options list after the equal sign to control which options are allowed for the option directive.

Since then, plus all and none, there are 7 optional values altogether. Seems to have grown a lot of insight Ah! Later on, no matter what Linux, I can easily find the problem!