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
22058	Consider a more general method to replace handlerXXX	Debanshu Kundu	ANUBHAV JOSHI	With class based views it's not straight forward to to raise a `Http404` error if the view doesn't support HTTP method (i.e. a 405 error), with function based views it was. So, in such cases clients (users) see a blank page with 405 response code, but with no message to tell them where to go from there. I guess Django should raise and handle `Http405` exception and use a default `handler405` view (which of course can be overridden) to return response to user in such a case, as it does in case of 404, 403 and 500 errors.	New feature	closed	Core (URLs)	dev	Normal	wontfix		anubhav9042@…	Accepted	1	0	0	0	0	0