[ThatRailsGuy]

Post below this one.

[Cyril]

It checks if the requested URL isn't a file or folder, and if it isn't, it rewrites the URL onto index.php

[Ruku]

<IfModule mod_rewrite.c>

If mod_rewrite is loaded...

    RewriteEngine On

Enable it for any files under this directory.

    RewriteBase /

Explicitly tell it to act relative to the web root; a fix needed for the ignorant masses who place trust in mod_security and probably others (it's a chocolate teapot).

    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d

Trigger it if no file (

-f

) or directory (

-d

) with the filename the request is for exists.

REQUEST_FILENAME

is parsed such that the GET parameter query string and FastCGI path info stuff is stripped.

    RewriteRule ^.+$ index.php [L]

Process the request by continuing as if the

REQUEST_FILENAME

were index.php. The

L

flag aborts any further processing of rewrite rules, forcing this match to take precedence.

</IfModule>

Duh

I did write up a quick post that had the most common Apache rewrite ruleset converted for nginx. I can go dig it out if you need it for anything?

[gibbonweb]

Ruku, thanks a bunch! +1 for the chocolate teapot, sounds yummy (I don't get the refernce, but that's fine )

I was able to convert that into a cherokee rule pretty easily - once my blog is up I'll post the resulting rule since it might be of interest for anyone with a similar setup.

[Ruku]

gibbonweb, on 04 February 2012 - 02:17 PM, said:

Ruku, thanks a bunch! +1 for the chocolate teapot, sounds yummy (I don't get the refernce, but that's fine )

I was able to convert that into a cherokee rule pretty easily - once my blog is up I'll post the resulting rule since it might be of interest for anyone with a similar setup.

Glad I could be of assistance

The chocolate teapot thing is just logic - if you tried to make tea in it, it'd melt. mod_security is equally useless in most situations, except for where the rules have been thought out and you're accommodating only certain apps (the cooler variety? heh).

[Daniel15]

As for Cherokee, there's several different ways to get a similar configuration. Here's one that I use, rules in this order:

1. PHP rule (added by Cherokee's wizard)
2. "File exists" rule, handler of "List and Send", "Match any file" ticked, set to "Final"
3. Change default rule to "Redirection" handler, with this rule:
- Type: Internal
- Regular expression: ^(.+)$
- Substitution: /index.php/$1

This is the set of rules that most closely matches that Apache configuration.

[gibbonweb]

Daniel15, on 04 February 2012 - 06:09 PM, said:

As for Cherokee, there's several different ways to get a similar configuration. Here's one that I use, rules in this order:

1. PHP rule (added by Cherokee's wizard)
2. "File exists" rule, handler of "List and Send", "Match any file" ticked, set to "Final"
3. Change default rule to "Redirection" handler, with this rule:
- Type: Internal
- Regular expression: ^(.+)$
- Substitution: /index.php/$1

This is the set of rules that most closely matches that Apache configuration.

Lol, I've done the inverse of your 2. and 3.:


1. PHP rule (added by Cherokee's wizard) (non final)
2. NOT "File exists" rule, "Redirection" handler (final)
3. default rule w/ "List & Send" handler.


...and I have yet to meet someone who can define what "final" vs. "non final" means...

[Daniel15]

Quote

Lol, I've done the inverse of your 2. and 3.:

Haha, that works too.

Quote

...and I have yet to meet someone who can define what "final" vs. "non final" means...

Final is the equivalent of the [L] flag in mod_rewrite rules. It means that once that rule is matched, no other rules will be applied to the request. With the rules I posted, if the second rule (File Exists) matches, you don't want to do the redirect, so it needs to be set to final.

The PHP rule only tells Cherokee how to handle files with "php" as the extension. It doesn't do anything else itself, which is why it's non-final. You can still apply redirects to .php requests, for example.

[gibbonweb]

Daniel15, on 05 February 2012 - 04:51 PM, said:

Haha, that works too.


Final is the equivalent of the [L] flag in mod_rewrite rules. It means that once that rule is matched, no other rules will be applied to the request. With the rules I posted, if the second rule (File Exists) matches, you don't want to do the redirect, so it needs to be set to final.

The PHP rule only tells Cherokee how to handle files with "php" as the extension. It doesn't do anything else itself, which is why it's non-final. You can still apply redirects to .php requests, for example.

Ha! Awesome. Thanks - that's not even in the docs like that (at least, I looked for this explanation and never found it )

[Daniel15]

You must be looking in the wrong place

From http://www.cherokee-...al_servers.html

Quote

Final: If this flag is present it means that no other rules will be applied after this one, even if the request also matches other rules with lower priority. The server will issue a response with whatever behavior it has figured out by then.