Looks like I nailed the reverse proxy arrangement, apologies to all on this mailing list, this particular issue isn't something specific to Django:
- Definitely do not need to configure SetRemoteAddrFromForwardedFor middleware ( http://code.djangoproject.com/browser/django/trunk/django/middleware/http.py?rev=11000#L33) in Django (not with nginx at least). - In nginx, the key bits in the config files are: # So this deals with host IP *and* port proxy_set_header Host $host:$server_port; proxy_redirect default; - What's neat is that you can use nginx and the default Django webserver for debugging, then switch a config setting in nginx, restart nginx and be using Apache. Tom - re: the admin on a separate port - thanks - sounds good. R On Oct 24, 12:46 pm, Tom Evans <tevans...@googlemail.com> wrote: > On Fri, 2009-10-23 at 10:05 -0700, rd-london wrote: > > > On a slightly separate note - forgetting the reverse proxy arrangment > > for a moment, how would one serve admin on a separate port? > > > Thanks for any help, > > R > > Can't help with the other bit, but - in apache or nginx? > > In apache you'd simply define a second vhost on a different port. In the > main vhost you would deny requests to /admin, and in the second vhost > deny requests not to /admin. > > Cheers > > Tom --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
