On Mon, Nov 5, 2012 at 7:20 PM, Magnus Hagander <magnus@hagander.net> wrote:
On Mon, Nov 5, 2012 at 6:50 PM, Marti Raudsepp <marti@juffo.org> wrote:
On Mon, Nov 5, 2012 at 7:44 PM, Magnus Hagander <magnus@hagander.net> wrote: > I guess the proper way to deal with it is to define our own view that just > has the @ssl_required decorator and then calls the django default view > directly.
Here's an untested patch to do that.
I was already working on that part and have applied a very similar patch. Let's hope we didn't both break it.
Forgot to credit you with figuring out the problem - sorry!
Turns out we were both badly mistaken on how easy that fix was. I've applied what I believe is a proper fix now, it certainly required anumber of more arguments than we had in there in the first place.
Are you looking into the CSRF error message issue, or should I?