Merge lp:~matt-goodall/canonical-identity-provider/new-account-head into lp:canonical-identity-provider/release
Proposed by
Matt Goodall
Status: | Merged |
---|---|
Approved by: | Natalia Bidart |
Approved revision: | no longer in the source branch. |
Merged at revision: | 1313 |
Proposed branch: | lp:~matt-goodall/canonical-identity-provider/new-account-head |
Merge into: | lp:canonical-identity-provider/release |
Diff against target: |
36 lines (+8/-0) 2 files modified
src/webui/tests/test_views_registration.py (+6/-0) src/webui/views/registration.py (+2/-0) |
To merge this branch: | bzr merge lp:~matt-goodall/canonical-identity-provider/new-account-head |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Natalia Bidart (community) | Approve | ||
Review via email: mp+266388@code.launchpad.net |
Commit message
Handle HEAD requests to the new account view.
Description of the change
Handle HEAD requests to the new account view. Fixes https:/
To post a comment you must log in.
Hi Matt!
Thanks for working on this. I'm a bit surprised by this solution, meaning that we usually don't allow HEAD requests to views that are not meant to HEAD to. IMHO, is also an odd pattern in django views to return the response for a GET in a HEAD.
What we usually do to solve the oops is decorate the view with @require_ http_methods( ['GET', 'POST']) to avoid this oopses (that will return 405 to caller on a HEAD request).
Do you see any reason not to do that in this branch?