Thanks for the explanation. We ended up re-arranging which pieces were listening on which ports so the nginx front end is on port 80. Reading the nginx docs, it seems like we might have been able to make our current set up do what we wanted, but shuffling the ports was easier :-)
Regarding: > The munging is I think being done by whatever web > server you're using (Apache? Nginx? It's hard to tell from your > description; you just say "Django on port 9200"), it's the built-in runserver for testing, gunicorn in production. On Aug 23, 2011, at 5:03 PM, Jacob Kaplan-Moss wrote: > On Tue, Aug 23, 2011 at 4:01 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: >> However, I believe it's not actually Django doing the rewriting. > > Scratch that: I'm wrong. Actually, Django *is* doing the re-writing: > see > https://code.djangoproject.com/browser/django/trunk/django/http/utils.py#L11. > > Still, the point stands that it's necessary -- standards and all that > -- and that you should be fixing it in your proxy layer. > > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > --- Roy Smith r...@panix.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
