-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
POST actions #16
Comments
you can do a POST request if you want, you have to make your own template to do it though. |
Would you be open to a PR to allow only posts (maybe per-action)? Without that, we're leaving the door wide open to cross site request forgeries. I'm not sure how to best go about doing this. In my experience trying to overload a list (ie, changing Maybe we can set a property on the action method itself?
|
The later is more of what I was thinking. I was also thinking of building in the boilerplate for handling permissions (right now you have to do it yourself, but it can get repetitive boilerplate). |
Have there been any thoughts about converting actions to POST requests rather than GET?
I found https://github.com/texastribune/django-object-actions/pull/2but it appears that's mostly on the serving side and not where the buttons are produced.
However, almost by definition an "action" should be initiated with a POST rather than a GET, both for semantics and security. Is there an easy way to do this? Any reasons not to?
James
The text was updated successfully, but these errors were encountered: