Hello,
Thanks for the quick reply. I apologize ahead-of-time if this is the
incorrect way to reply to messages on here. I have my notification
settings
set to once per day.
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? Basically, when the user accesses
username.example.com/foo/bar/then my WSGI Application would just see "
example.com/username/foo/bar/". I’m trying to get around a limitation of
django where it processes URLs based on the path alone. I mainly want
this
done dynamically so I don’t have thousands of configuration directives
going on.
Thanks again!
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 D. [email protected]