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
18373	Thoroughly misleading error page when resolve() fails on a different URL	anonymous	Grzegorz Nosek	"I just spent a few hours tracking down a display bug in djangorestframework (https://github.com/tomchristie/django-rest-framework/pull/211).

This would have been *much* simpler if the debugging 404 error page hadn't been presenting this entirely irrelevant piece of information the whole time:

    ""The current URL, api/servers/, didn't match any of these.""

As far as I can tell, the error page is getting that URL from the request's path_info attribute, when the real problem was that djangorestframework was doing ""resolve(request.path)"".

It would be better if the resolver set the URL it was trying to resolve on the Http404 exception object and the debugging error template retrieved it from there, rather than assuming that every 404 it is asked to display relates to the current page."	Cleanup/optimization	closed	Core (URLs)	1.3	Normal	fixed		amirouche.boubekki@…	Accepted	1	0	0	0	0	0