CSRF still can break serve_rpc_request in 0.1.7
Bug #658788 reported by
David Chandek-Stark
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| RPC4Django |
Fix Released
|
Medium
|
davidfischer | ||
Bug Description
I found after upgrading to Django 1.2 that I was having intermittent problems with rpc4django 0.1.7 and Django's CSRF functionality. I haven't tested this, but I think the solution is to move a block of code in views.py as show in the attached diff file.
Revision history for this message
| David Chandek-Stark (dchandekstark) wrote | #1 |
| Changed in rpc4django: | |
| assignee: | nobody → davidfischer (djfische) |
| milestone: | none → 0.1.8 |
Revision history for this message
| davidfischer (djfische) wrote | #2 |
| Changed in rpc4django: | |
| importance: | Undecided → Medium |
| status: | New → Fix Released |
To post a comment you must log in.
This is implemented in 0.1.8. Thanks for the patch!