id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
34106	Allow LogoutView to render a confirmation template on a GET request (Like LoginView)	Nick Mow	nobody	"LoginView has a very reasonable workflow IMO. A GET request renders a template. Submitting the form produces a POST request, which then creates the user and issues a redirect.

LogoutView is currently undergoing a deprecation process for GET requests, which I believe is somewhat misguided. The idea to prevent logouts via GET request is a good one IMO. However, I think that the GET request should be preserved to render a ""logout confirmation"" template if desired (and perhaps bypassed with an boolean attribute like 'require_confirmation' or something of the sort).

If this is done, the desired behavior behind the changes (no logout via GET request) is preserved. It also leaves room for a ""logout confirmation"" template, which would harmonize the LogoutView behavior with that of the LoginView. If a user doesn't want any logout confirmation, they could set/unset the 'require_confirmation' boolean to easily get the desired behavior.

I think this strategy would dovetail well with some of the changes that have been made to LogoutView during the 4.x releases, ie. making the behavior of LogoutView more like any other FormView (e.g. renaming get_next_page() to get_success_url()). This would also reduce the cognitive burden of having to deal with unnecessarily (?) specialized view behavior."	New feature	closed	contrib.auth	4.1	Normal	wontfix	logout, logoutview, formview		Unreviewed	0	0	0	0	0	1