[Improvement Request] htaccess-lite for nginx
pascal.nitsche at fansubcode.org
Wed Dec 8 16:37:00 MSK 2010
Am 08.12.2010 14:23, schrieb Grzegorz Nosek:
> W dniu 08.12.2010 14:07, Pascal Nitsche pisze:
>> Because there are some hosting systems beginning to support nginx (ex.
>> Froxlor - http://froxlor.org) and it is not really practical to have
>> customers have to submit a support ticket for every single rewrite they
>> need etc I thouight nginx could be improved by something like
> We considered that some time ago, wrote some patches, ended up
> proxying to Apache everything except a well-defined set of static file
> extensions (and 404s for rewrites).
> Not being fully Apache-compatible frustrates your users as they have
> to learn a new syntax and -- this is the major problem -- cannot use
> ready-made apps with bundled .htaccess files. By the time you end up
> mostly compatible, you will have implemented half of Apache anyway.
> Best regards,
> Grzegorz Nosek
> nginx-devel mailing list
> nginx-devel at nginx.org
I didn't know you already discussed this some time ago, my apologies for
rewarming this topic.
But I don't think it's good to proxy to apache for that because it's
making the performance improvement by using nginx go to hell mostly.
And I think it's more annoying to have to write a ticket to the admin
for each rewrite or other light configuration change then to learn
simple (and clean!) nginx syntax (or copy/paste from some docs).
Also I didn't mean to be full compatible - I just suggested a
possibility to load user-written configurations without worrying about
misconfiguration and security breaches.
If this would be possible I think the great apps (Wordpress, Joomla etc)
would have documentation on how to setup if using nginx really fast and
the more nginx will be used by hostes the more documentation on that
will be written for not as well known apps as Wordpress or Joomla or Typo3.
I still think it would be an improvement many people could have a need
of (myself included) and would be a nice feature.
Since not everyone will need it I also thought of making it optional to
compile in as I wrote in the default settings it could be turned off for
At the moment the lack of some kind of possibility to add rewrites etc.
dynamicly by the customer is the greatest thing preventing me from
banning apache2 or at least reducing its use to only the apps that
REALLY DO NEED apache functionalities (ex. Redmine Perl Auth for SVN is
only available for Apache) from my box and gain some speed and
performance from nginx.
More information about the nginx-devel