I have a PHP application that runs just fine, but when I try to set up a short-URL rewrite it breaks. Here's the original stanza for the virtual server, with long URLs:

server {
listen 80;
server_name example.com;
access_log /path/to/log main;
location / {
root /path/to/example.com;
index index.html index.php;
}
location ~ \.(html|php) {
include /path/to/fastcgi.conf;
root /path/to/example.com;
fastcgi_pass 127.0.0.1:12345;
fastcgi_index index.php;
}
}

Now, I have an application (Gallery 3) in a subdirectory of example.com, so the URLs are e.g. http://www.example.com/gallery3/... and the files are at /path/to/example.com/gallery3/... The rewrite, of course, should apply only to documents in the gallery3 directory. I tried adding the following stanza above location~ \.(html|php):

location ~ /gallery3/ {
if (!-e $request_filename) {
rewrite ^(.*)$ index.php?kohana_uri=$1 last;
}
}

I've tried a bunch of variations on this, but no luck. All generate 404 errors or "No input file specified." What am I missing?

Many thanks,
androo

Okay, I figured it out. For the record:

1. The rewrite stanza has to go after, not before, the php stanza.

2. Also, with G3 at /home/gallery3/, the rewrite stanza has to look like this:

location ~ /gallery3/ {
root /home;
index index.html index.php;
if (!-e $request_filename) {
rewrite ^/gallery3/(.*)$ /gallery3/index.php?kohana_uri=$1 last;
}
}

Hope that helps anyone else who may be wondering.

You may find it more efficient with a "try_files" directive.

[code]
location ~ /gallery3/ {
root /home;
index index.html index.php;
try_files $uri $uri/ /gallery3/index.php?kohana_uri=$1;
}
[/code]

--
Jim Ohlstein

Interesting idea. Is try_files less resource-intensive? Just curious why it would be more efficient.

androo Wrote:
-------------------------------------------------------
> Interesting idea. Is try_files less
> resource-intensive?

Yes

Just curious why it would be
> more efficient.

It has to do with how requests are parsed. Igor is [b]ADAMANT[/b] about it (he really hates using "if's" in these situations). In order to understand exactly I suspect that I would need to be an experienced C programmer - or even a passable one, something I am not.

--
Jim Ohlstein