On Sat, Sep 24, 2011 at 9:28 PM, Luke Plant <[email protected]> wrote: > > I'm happy to be proved wrong, of course. Apache is very popular, though, > so if its hard in Apache, it could be said to be hard full stop. >
RequestHeader unset X-Forwarded-Protocol Not precisely what I'd call hard. >From a-business-that-uses-this-sort-of-stuff POV, we don't really mind if this is fixed in Django at all. A lot of the enterprise bits that our architecture needs (SetRemoteAddrFromForwardedFor, SSL middleware) was either missing, or crippled with no intention to fix it (SetRemoteAddrFromForwardedFor couldn't handle being behind multiple proxies and was finally dumped). It was pointed out to us that what we do is not particularly like the majority of users, so we have been maintaining our own middleware classes that updates or monkey patches the request object with the appropriate info. I suppose it is analogous to DB routers. Django doesn't provide routers to handle the common ways to scale a database, but they are simple enough to write for your specific setup. There is a simple way to add your own fixups to requests, and it works, so we don't need to burden the core or contrib with it. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
