Why not remove csrfmiddlewaretoken in CsrfViewMiddleware from request.POST?

I have various views which break on the additional csrfmiddlewaretoken in request.POST when using the recommendet CSRF protection with CsrfViewMiddleware and {% csrf_token %}. Why don't we just remove the csrfmiddlewaretoken in CsrfViewMiddleware before the request hits the views? patch on middle

Why not remove csrfmiddlewaretoken from request.POST?

I have various views which break on the additional csrfmiddlewaretoken in request.POST when using the recommendet CSRF protection with CsrfViewMiddleware and {% csrf_token %}. Why don't we just remove the csrfmiddlewaretoken before the request hits the views? patch on middleware/csrf.py 1.2.1 fin

Re: Missing REFERENCES... in SQL of models.ForeignKey('LaterDefinedModel')

On Jan 31, 2:31 am, Malcolm Tredinnick wrote: > On Sat, 2009-01-31 at 12:20 +1100, Malcolm Tredinnick wrote: > > On Fri, 2009-01-30 at 09:49 -0800, mucisland wrote: > > > Hi all. > > > > If I specify the ForeignKey target model as a string because it is not > &

Missing REFERENCES... in SQL of models.ForeignKey('LaterDefinedModel')

Hi all. If I specify the ForeignKey target model as a string because it is not yet defined, the (SQLite3) SQL table entry misses the REFERENCES specifier. Example: class Department(models.Model): head = models.ForeignKey('Person', related_name='heads') class Person(models.Model): departm