. Htaccess: RewriteEngine not allowed here Solution

Author: North
 
# In fact, this article has leaked a lot of information, but I still want to write this solution process to my friends who will encounter the same problem later. You don't want to hack me ......
 
The blog server itself is not in China, and the access volume is much slower. Creating a cache should reduce the pressure on programs and databases. So yesterday, a plug-in named wp-super-cache was installed, after installation, it cannot be used normally. First, there are various permission problems. After the solution, it seems like it is okay?
 
However, today, we suddenly found that only WP-Cache is working, and WP-Super-Cache is mentally retarded ......
 
After carefully reading the error log, I found that too many functions are disabled in php. ini. After these functions are enabled, it seems to work, but sometimes 500 is accessed!
 
This must not be tolerated. Make up your mind to fix it today, no matter what time!
 
Again, log discovery is similar.
 
[Tue May 01 01:17:20 2012] [alert] [client x. x]/x/xblog/wp-content/cache/. htaccess: RewriteEngine not allowed here
I wiped it, and the permission settings were too dead. Previously, AllowOverride FileInfo was set for. htaccess rewrite. Why is there a problem?
 
Google, there is basically no relevant content in China, foreigners are advised to directly modify the apache configuration file AllowOverride Indexes or All:
 
Http://www.masterblanker.com/2010/03/22/wp-supercache-and-error-500/
 
Http://speedforce.org/2009/01/were-back/
 
Is this a pitfall, or a pitfall ...... Isn't it a random column directory? These articles have certainly put a lot of people into it.
 
Therefore, I plan to write a permission similar to setting permissions for sub-directories separately. For example:
 
<Directory/x/xblog/wp-content/cache>
Options + Indexes FollowSymLinks
AllowOverride Indexes FileInfo
</Directory>
At this time,/wp-content/cache can be a column directory, but other directories cannot be a column. In fact, this can be tolerated, but I remember the ghost also used this plug-in, so I ran to see his
 
Http://huaidan.org/wp-content/cache/
 
Oh, 403, it seems that I still haven't set it up. I seem to have written more Options + Indexes FollowSymLinks, so I tried to write only one AllowOverride Indexes FileInfo sentence ......
 
Apache, nginx, and other things are usually compiled and installed, and can be directly used for security configuration. If the configuration is too detailed, you can't think of it as a matter of detail, now I have spent some time studying it carefully. Is this the legendary O & M? --
 
I wrote too much nonsense and finally wrote it.
 
<Directory/x/xblog/wp-content/cache>
AllowOverride Indexes FileInfo
</Directory>
You can.
 
I don't know if there is any problem with this configuration. For now, there is no problem in my blog. If you think there is a problem, please let me know. Thank you!