search

anikesh / web-optimizator

Automatically exported from code.google.com/p/web-optimizator
0 stars 0 forks source link

htaccess vs non-Apache #579

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
.htaccess is not used by nginx or lightd.
Please support.

Original issue reported on code.google.com by yves.lav...@gmail.com on 1 Apr 2012 at 11:23

GoogleCodeExporter commented 9 years ago 
nginx doesn't support any substitution for .htaccess and there are optimization 
rules for nginx config here
http://code.google.com/p/web-optimizator/wiki/IntegrationWithWebsite

Original comment by sunny.dr...@gmail.com on 2 Apr 2012 at 2:05

GoogleCodeExporter commented 9 years ago 
I know that Nginx doesn't support .htaccess, yet Webo still proposes settings 
although it is able to know that it is running under Nginx and not Apache.
That's what I was meaning by "please support", i.e. react accordingly. 
htacccess is meaningless for Nginx.

Original comment by yves.lav...@gmail.com on 29 May 2012 at 1:03

GoogleCodeExporter commented 9 years ago 
if no Apache modules are available - product options are changed accordingly.
Do you say, that there can be some option 'Nginx rules added', which will 
indicate if all possible client-side features are supported already (via nginx 
configuration, which can be changed by admin / developer) and we don't need to 
emulate them with raw PHP?

Original comment by sunny.dr...@gmail.com on 29 May 2012 at 6:55

GoogleCodeExporter commented 9 years ago

Original comment by sunny.dr...@gmail.com on 16 Sep 2012 at 9:12