Hi Paul,
If you want the admin site to behave differently than the main site, you
could consider running two instances, one with the i18n activated for the
main site, and one for admin users with it disabled. In production, from a
security standpoint, it's a good idea to have the admin site run
Hey Web Architect, I guess you never got that DB dump running in
development? ;-)
Why don't you run some profiling middleware to see if you can some traces
of the production system? Or how about New Relic or some such? That's
pretty good at helping to identify problems spots in your stack.
Fin
issue can be fixed without cause security problems
> but I'm not sure. Please follow
> https://code.djangoproject.com/ticket/26158 and related Python tickets.
>
> On Friday, February 5, 2016 at 3:13:14 AM UTC-5, Will Harris wrote:
>>
>> Hey Daniel,
>>
>>
Hey Daniel,
Thanks for the reply. Unfortunately doing this in a custom middleware is
not an option, as the this processing needs to take place at a very low
level, at the point where the Request object is being built. By the time
the request is passed in to the middleware layers for processing,
4 matches
Mail list logo