 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
15 messages in ru.sysoev.nginxRe: correct usage of location context?| From | Sent On | Attachments |
|---|---|---|
| Szymon Polom | Jun 12, 2009 9:05 am | |
| lejeczek | Jun 12, 2009 10:22 am | |
| Cliff Wells | Jun 12, 2009 10:54 am | |
| Szymon Polom | Jun 12, 2009 11:01 am | |
| Szymon Polom | Jun 12, 2009 11:31 am | |
| Nick Pearson | Jun 12, 2009 11:57 am | |
| Cliff Wells | Jun 12, 2009 12:07 pm | |
| Cliff Wells | Jun 12, 2009 12:14 pm | |
| Igor Sysoev | Jun 12, 2009 12:18 pm | |
| Szymon Polom | Jun 12, 2009 12:35 pm | |
| Szymon Polom | Jun 12, 2009 2:01 pm | |
| Rob Schultz | Jun 12, 2009 6:35 pm | |
| Igor Sysoev | Jun 12, 2009 9:53 pm | |
| Avleen Vig | Jun 13, 2009 7:45 am | |
| Szymon Polom | Jun 13, 2009 8:18 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: correct usage of location context? | Actions... |
|---|---|---|
| From: | Nick Pearson (nick...@gmail.com) | |
| Date: | Jun 12, 2009 11:57:25 am | |
| List: | ru.sysoev.nginx | |
If you want to map a request to /test/x to /var/www/test/x instead of /var/www/test/test/x, it sounds like you need a rewrite to remove "/test" from the request URI. There may be another way of doing this, but basically:
... location /test { root /var/www/test; rewrite ^/test(.*)$ $1; } ...
That will get rid of the "duplicate" /test in the final path nginx uses to access the filesystem. Also note that the new regular expression support in the "location" should make it easy to have a single block (like above) for many sites.
Nick
On Fri, Jun 12, 2009 at 1:31 PM, Szymon Polom <sp...@winterstille.net> wrote:
Cliff Wells wrote:
On Fri, 2009-06-12 at 18:23 +0100, lejeczek wrote:
would not it be a trailing(redundant) slash in location statement? - location /test
1. The trailing slash doesn't matter, /test looks for either a file or directory (that's what nginx's error-log says to me at least). It shouldn't be looking for /test though, it should list/process the content from the filesystem as set by the root parameter (/var/www/test).
Also his root settings are wrong:
location /test { root /var/www; }
2. My root-settings are not wrong. I have many sites in /var/www and test should not be mapped to /var/www but to /var/www/test.
With that mapping, I assume that calling http://example.com/test/foobarshould
try to access /var/www/test/foobar on the filesystem and not
/var/www/test/test/foobar like it does now.
What I'm trying to achieve is to move away from a vhost-configuration to a multiple-apps/sites-configurations, e.g.
example.com/railsapp1/* would access /var/www/railsapp1 and below only, example.com/railsapp2/* would access /var/www/railsapp2 and below only, example.com/phpapp1/* would access /var/www/phpapp2 and below only, example.com/ would access /var/www/static_html and below unless below is one of the above mentioned "virtual" URIs.
PS: It's "awesome" how slow this mailing list is (I don't mean the response time, but the time the system managing this list takes to process an email and to deliver it out to subscribers).