Sorry meant to add. Key sources of information:
- http://wiki.nginx.org/NginxHttpProxyModule#proxy_redirect
- http://forum.slicehost.com/comments.php?DiscussionID=3065
R
On Oct 24, 8:58 pm, rd-london wrote:
> Looks like I nailed the reverse proxy arrangement, apologies to all on
> this mailin
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/middlewar
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 simp
Right, well, replying to myself ... and hoping someone else will jump
in, here's where I'm upto ...
Having read around a bit, I figured that the reverse proxy my well be
losing the original IP address, so I looked into configuring
"SetRemoteAddrFromForwardedFor" (http://code.djangoproject.com/bro
Hi,
Wonder if someone can help.This issue is all with a local dev
situation, so this isn't live.
I have nginx running on port 81 e.g. http://127.0.0.1:81/ and serving
static media - which in turn proxies through to Apache running on port
96. All works fine (apart from the issue I outline below) -
5 matches
Mail list logo