[Resolved] Lightspeed and hosting provider - Fails

M

Morpheus

Member
#1
#1
All of the sudden my website started failing to display items and after tinkering awhile i commented out the htaccess files that had 'Deny from all' in them and my site went back to normal. I contacted my hosting provider TMDHosting and they came back with this:

----------\
It seems that there should be an issue with some of the rewrite URLs your website is using and the LightSpeed http service running on the server. The options to have the issue resolved are:

1. You may request from your website developers to recreate the rewrite rules for the website compatible with LightSpeed web service.
2. If you would like we will migrate your website to a server with normal Apache. If all the rewrite URLs are correct for the regular Apache web service the issue should be resolved.
----------/

I'm running a Zikula website. Here is what the htaccess looks like:

File: $Id: .htaccess 26262 2009-08-20 05:35:53Z drak $
# ----------------------------------------------------------------
# Purpose of file: block any web access to files stored under
# the modules/ directory
# ----------------------------------------------------------------
SetEnvIf Request_URI "\.css$" object_is_css=css
SetEnvIf Request_URI "\.js$" object_is_js=js
SetEnvIf Request_URI "\.jpg$" object_is_jpg=jpg
SetEnvIf Request_URI "\.gif$" object_is_gif=gif
SetEnvIf Request_URI "\.png$" object_is_png=png
SetEnvIf Request_URI "\.tif$" object_is_tif=tif
SetEnvIf Request_URI "\.swf$" object_is_swf=swf
SetEnvIf Request_URI "\.flv$" object_is_flv=flv
SetEnvIf Request_URI "\.ico$" object_is_ico=ico
SetEnvIf Request_URI "\.cur$" object_is_ico=cur
Order deny,allow
Deny from all
Allow from env=object_is_css
Allow from env=object_is_js
Allow from env=object_is_jpg
Allow from env=object_is_gif
Allow from env=object_is_png
Allow from env=object_is_tif
Allow from env=object_is_swf
Allow from env=object_is_flv
Allow from env=object_is_ico
Allow from env=object_is_cur

I'm really not sure what I need to do here other then having them move my website?
 
Last edited by a moderator:
N

NiteWave

Administrator
#4
#4
try this in .htaccess:
Code: 
RewriteEngine On
RewriteCond %{Request_URI} !\.(css|js|jpg|gif|png|tif|swf|flv|ico|cur)$
RewriteRule (.*)	- [F]
 
M

Morpheus

Member
#5
#5
NiteWave said:
try this in .htaccess:
Code: 
RewriteEngine On
RewriteCond %{Request_URI} !\.(css|js|jpg|gif|png|tif|swf|flv|ico|cur)$
RewriteRule (.*)	- [F]
Click to expand...
Ok,

The only thing in the htaccess file is what you posted. I'm not actually sure what this does. How can I tell if it's working? What exactly is it doing?

Thanks...
 
N

NiteWave

Administrator
#6
#6
How can I tell if it's working? What exactly is it doing?
Click to expand...
only files with one of extensions --- css|js|jpg|gif|png|tif|swf|flv|ico|cur are allowed to access under this folder and all sub folders.

otherwise, access to files with other extensions will return "403 Forbidden"
 
M

Morpheus

Member
#7
#7
The problem occurred when my host apparently installed lightspeed. The changes you suggest, I did just completed on all my htaccess files that were formatted similar to the one I posted. Some only had html and some had gif,png,jpg. I formatted each to the example you gave to include the extensions that were only included in that particular htaccess file. All seems to be working. Now if for whatever reason my host needs to transfer my site to a non-lightspeed server will the changes I made be compatible?

The htaccess files were the original from my CMS. Should the developers be releasing the CMS with these changes to be more robust for the end user?

Thanks...
 
N

NiteWave

Administrator
#8
#8
Now if for whatever reason my host needs to transfer my site to a non-lightspeed server will the changes I made be compatible?
Click to expand...
yes, they are apache directives. as long as the web server is apache or litespeed, these directives works.

Should the developers be releasing the CMS with these changes to be more robust for the end user?
Click to expand...
you can suggest them. despite of efficiency, at least the code is shorter than original one.
 
Last edited:
M

Morpheus

Member
#9
#9
I think two more quick questions;

1) Do in need to start out each htaccess file with 'RewriteEngine On'?

2) I wasn't sure about this 'you can suggest them. despite of efficiency'; are you saying that the new way is more or less effecient?

:)

Thank you so much for the help.
 
N

NiteWave

Administrator
#10
#10
1)yes.if no "RewriteEngine On", RewriteCond or RewriteRule won't work and will be ignored. However, if .htaccess has no RewriteCond or RewriteRule, you needn't "RewriteEngine On".

2)I think the new way is more efficient and obviously. However, I haven't tested it so without hard evidence...
 
B

brrr

Well-Known Member
#11
#11
I am assuming this means directives like this in .htaccess will also fail to function under Litespeed:

Code: 
BrowserMatchNoCase ^WWW-Mechanize BadRobot
BrowserMatchNoCase ^Xenu BadRobot
BrowserMatchNoCase "Y!OASIS/TEST" BadRobot
BrowserMatchNoCase "YebolBot" BadRobot
BrowserMatchNoCase "ZeW" BadRobot
BrowserMatchNoCase ^Zip BadRobot
BrowserMatchNoCase "ZmEu" BadRobot

<Files *>
Order Allow,Deny
Allow from all
Deny from env=BadRobot
</Files>
That could mean some hassles.
 
N

NiteWave

Administrator
#12
#12
The rewrite equivalence:
Code: 
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^(WWW-Mechanize|Xenu|Zip) [OR,NC]
RewriteCond %{HTTP_USER_AGENT} .*(Y!OASIS/TEST|YebolBot|ZeW|ZmEu).* [NC]
RewriteRule (.*) - [F]
 
B

brrr

Well-Known Member
#13
#13
Thank you for that code NiteWave. Much appreciated. It will help out some users who relied on .htaccess under Apache to do bot-blocking.
 
M

Morpheus

Member
#14
#14
NiteWave said:
1)yes.if no "RewriteEngine On", RewriteCond or RewriteRule won't work and will be ignored. However, if .htaccess has no RewriteCond or RewriteRule, you needn't "RewriteEngine On".

2)I think the new way is more efficient and obviously. However, I haven't tested it so without hard evidence...
Click to expand...
I think we almost got what we need but trying to be, I guess, backward compatable? This seems to fail at the if statements. Does this look right, or suggestions?

Code: 
# Default to the mod_rewrite method, since it seems more efficient.
<IfModule rewrite_module>
    RewriteEngine On
    RewriteCond %{Request_URI} !\.(css|js|jpg|gif|png|tif|swf|flv|ico|cur)$ [NC]
    RewriteRule .* - [F]
</IfModule>

# If mod_rewrite is not loaded, fall back to mod_setenvif method.
<IfModule !rewrite_module>
    SetEnvIf Request_URI "\.css$" object_is_css=css
    SetEnvIf Request_URI "\.js$" object_is_js=js
    SetEnvIf Request_URI "\.jpg$" object_is_jpg=jpg
    SetEnvIf Request_URI "\.gif$" object_is_gif=gif
    SetEnvIf Request_URI "\.png$" object_is_png=png
    SetEnvIf Request_URI "\.tif$" object_is_tif=tif
    SetEnvIf Request_URI "\.swf$" object_is_swf=swf
    SetEnvIf Request_URI "\.flv$" object_is_flv=flv
    SetEnvIf Request_URI "\.ico$" object_is_ico=ico
    SetEnvIf Request_URI "\.cur$" object_is_cur=cur
    Order deny,allow
    Deny from all
    Allow from env=object_is_css
    Allow from env=object_is_js
    Allow from env=object_is_jpg
    Allow from env=object_is_gif
    Allow from env=object_is_png
    Allow from env=object_is_tif
    Allow from env=object_is_swf
    Allow from env=object_is_flv
    Allow from env=object_is_ico
    Allow from env=object_is_cur
</IfModule>
 
N

NiteWave

Administrator
#15
#15
tested your code in local lsws, it's working.

but I think the 2nd part
<IfModule !rewrite_module>
really not necessary. it adds extra overhead.
mod_rewrite is a very basic module and it's hard to imagine apache without rewrite module existing in any hosting provider.
 
M

Morpheus

Member
#16
#16
It seems that Lightspeed is processing all IFModule statments. If the first IFModule statement is true, then it should gracefully exit without running the second IFModule routine, but it doesn't. Is there a way to accomplish this?

Also how do you create a rewrite rule that will replace this:

# ----------------------------------------------------------------------
# Purpose of file: block any web access to files stored under
# the downloads_upload directory
# ----------------------------------------------------------------------
Order deny,allow
Deny from all
Click to expand...
 
N

NiteWave

Administrator
#17
#17
I think need go through .htacess, since there may be other directives in the file.

A rewrite equivalent for "Deny from all":
Code: 
RewriteEngine On
RewriteRule .* - [F]
 
M

Morpheus

Member
#18
#18
NiteWave said:
I think need go through .htacess, since there may be other directives in the file.

A rewrite equivalent for "Deny from all":
Code: 
RewriteEngine On
RewriteRule .* - [F]
Click to expand...

In the below example only, after the first IFModule statement is read it should exit before reading in the next IFModule statement but it doesn't. Is there a way to do this in the htaccess file?

Code: 
<IfModule rewrite_module>
    RewriteEngine On
    RewriteCond %{Request_URI} !\.(css|js|jpg|gif|png|tif|swf|flv|ico|cur)$ [NC]
    RewriteRule .* - [F]
</IfModule>

<IfModule !rewrite_module>
RewriteEngine On
RewriteRule .* - [F]
</IfModule>
 
You must log in or register to reply here.
Top