FilesMatch & php .htaccess options
- Thread starter priestjim
- Start date
Then, you should not mix them together, it only make it harder to identify the cause of the problem.
The screen shot shows that the redirect is actually sent by PHP, LSWS is just the messenger.
What the actually command of "HEAD"? I think it is just a command alias.
I tried "curl -I mp3smackers.com", it works fine.
"lynx -head -mime_header http://www.mp3smackers.com" also works.
Not sure, as my firefox never has problem with this site from beginning.
Which browser you used?
The screen shot shows that the redirect is actually sent by PHP, LSWS is just the messenger.
What the actually command of "HEAD"? I think it is just a command alias.
I tried "curl -I mp3smackers.com", it works fine.
"lynx -head -mime_header http://www.mp3smackers.com" also works.
Not sure, as my firefox never has problem with this site from beginning.
Which browser you used?
Let me introduce my self, I'm X-Nitro 2nd Administrator of DraCoola Multimedia. This bugs only occured on Wordpress Instalation. For example, like some pictures below :
!= Wordpress :
MyBB Bulletin Board
Now, I will try get header information from some victims (checked at 08:13 GMT+7)
And then, I'll try to get header information again from some victims above.
Automatic Cured, huh ?
Now, other victims appeared.
http://idwz.net
http://moviedb.asia
Complete .htaccess for idwz.net (Permalinks: /downloads/%postname%.aspx) :
Complete .htaccess for moviedb.asia (Permalinks: /%postname%.aspx/?%post_id%.download) :
I'm desperate.
!= Wordpress :
Code:
$ curl -I dracoola.comMyBB Bulletin Board
Code:
$ curl -I kikil.orgNow, I will try get header information from some victims (checked at 08:13 GMT+7)
And then, I'll try to get header information again from some victims above.
Automatic Cured, huh ?
Now, other victims appeared.
http://idwz.net
http://moviedb.asia
Complete .htaccess for idwz.net (Permalinks: /downloads/%postname%.aspx) :
PHP:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
PHP:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Accessing
http://idwz.net
http://moviedb.asia
there is no problem(infinite loop). Already resolved without any change?
with following rewrite rule only:
I tested latest lsws 4.0.4(standard version) and apache 2.2.11
None will cause infinite redirect loop.
Are there any other possible rewrite rules applied?
I noticed:
http://idwz.net/a
http://idwz.net/b
i.e., a single letter following http://idwz.net/ will redirect to other page;
while 2 letters etc will go "Not Found"
http://idwz.net/aa -- Not Found
http://idwz.net/bb -- Not Found
maybe this is a wordpress module, and has conflict with the .htaccess?
Just a guess.
http://idwz.net
http://moviedb.asia
there is no problem(infinite loop). Already resolved without any change?
with following rewrite rule only:
I tested latest lsws 4.0.4(standard version) and apache 2.2.11
None will cause infinite redirect loop.
Are there any other possible rewrite rules applied?
I noticed:
http://idwz.net/a
http://idwz.net/b
i.e., a single letter following http://idwz.net/ will redirect to other page;
while 2 letters etc will go "Not Found"
http://idwz.net/aa -- Not Found
http://idwz.net/bb -- Not Found
maybe this is a wordpress module, and has conflict with the .htaccess?
Just a guess.
Have you enabled disk cache? If yes, you should disable it for now.
I think it caches response for request http://www.mp3smackers.com/, which redirects to http://mp3smackers.com/
I think it caches response for request http://www.mp3smackers.com/, which redirects to http://mp3smackers.com/
It is the LSWS disk cache feature, not WP cache plugin, disabled it for now.
The problem that WP redirect www.domain.com to domain.com, if LSWS cache the redirect, it will cause trouble. We have to change the cache code to put requests to www.domain.com and domain.com in two separate cache.
The problem that WP redirect www.domain.com to domain.com, if LSWS cache the redirect, it will cause trouble. We have to change the cache code to put requests to www.domain.com and domain.com in two separate cache.