I'm using nginx as a HTTP proxy in front of a Werkzeug app. The nginx
config is either:
location /xxx/ {
rewrite /xxx/(.*) /$1 break;
proxy_pass http://127.0.0.1:5000;
}
or the same without the "rewrite" line.
In the first case, /xxx/info goes to http://127.0.0.1:5000/info and my
app will service it well. The problem is that Request.is_behind_proxy
is still false, and the question about creating urls is unanswered (to
me at least).
In the case without the rewrite, my app get's the full url like:
http://127.0.0.1:5000/xxx/info and it's not designed to accept that.
AFAIK some middleware could solve that problem, so should I go that
route? Does Werkzeug include some fixup middleware like that?
thanks
ps.
http://werkzeug.pocoo.org/documentation/0.5.1/deployment/index.html
lacks the information about deploying under nginx with HTTP proxing
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pocoo-libs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pocoo-libs?hl=en
-~----------~----~----~----~------~----~------~--~---
