2 messages in ru.sysoev.nginxRe: Rewrite Subdomains to Paths (Vale...| From | Sent On | Attachments |
|---|---|---|
| Kurtis Mullins | Mar 26, 2012 7:14 am | |
| Francis Daly | Mar 26, 2012 9:28 am |
| Subject: | Re: Rewrite Subdomains to Paths (Valentin V. Bartenev) | |
|---|---|---|
| From: | Francis Daly (fran...@daoine.org) | |
| Date: | Mar 26, 2012 9:28:11 am | |
| List: | ru.sysoev.nginx | |
On Mon, Mar 26, 2012 at 10:14:53AM -0400, Kurtis Mullins wrote:
Hi there,
Anyways, this would definitely work for redirects. Is it possible to do it in a way that is transparent to the end-user and my WSGI Application server?
That's (mostly) up to your application server.
Basically, when the user accesses username.example.com/foo/bar/then my WSGI Application would just see " example.com/username/foo/bar/".
On the nginx side, you "just" adjust the uwsgi_param values that you send. (Assuming that's how nginx access the application.)
But before you do that: try accessing the WSGI Application using the example.com/username/foo/bar/ style urls. Look in the returned content. Do you see the string "username" anywhere? Do you see any linked content with a url that starts "/" or with multiple "../"? Do you see any linked content with a url that includes "example.com"?
If you do, consider how they will look to a client which thinks that its initial request was to username.example.com/foo/bar.
You can get nginx to mangle http headers. You shouldn't get nginx to mangle the http body.
It can work. But it is worth testing your particular setup to make sure that it works for you.
f
-- Francis Daly fran...@daoine.org
_______________________________________________ nginx mailing list ngi...@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx