Actually, what am I saying -- CSRF doesn't make sense without some sort of session ID. So I guess we default to using the ID in the session module but allow people to sub in their own if they're not using that module.
I think we should probably use approach 1 in https://www.isecpartners.com/files/CSRF_Paper.pdf which gives us an excuse to change the name of the function. So the API would probably be something like: template: <form method="post" action="/purchase"> $csrf('purchase') ... </form> controller: i = web.inputs('purchase', ...) -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
