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
31724	django.urls.resolve ignores the FORCE_SCRIPT_NAME setting.	Pēteris Caune	nobody	"I suspect the `django.urls.resolve` function is not taking in account the FORCE_SCRIPT_NAME setting.

First, with FORCE_SCRIPT_NAME=None, I can do the following in `manage.py shell`:

{{{
>>> from django.urls import resolve, reverse
>>> reverse(""hc-docs"")
'/docs/'
>>> resolve(reverse(""hc-docs""))
ResolverMatch(func=hc.front.views.serve_doc, args=(), kwargs={}, url_name=hc-docs, app_names=[], namespaces=[], route=docs/)
}}}

In the above example, I can feed the result of `reverse` back into `resolve` and it works as expected.

Now with FORCE_SCRIPT_NAME='/foo':

{{{
>>> from django.urls import resolve, reverse
>>> reverse(""hc-docs"")
'/foo/docs/'
>>> resolve(reverse(""hc-docs""))
Traceback (most recent call last):
(...)
    raise Resolver404({'tried': tried, 'path': new_path})
}}}

Here, `reverse` added the ""/foo"" prefix to the URL, but `resolve` didn't seem to recognize it.

I suspect this is a bug but not sure. How is `django.urls.resolve` expected to behave here? "	Bug	closed	Core (URLs)	3.0	Normal	invalid		Florian Apolloner	Unreviewed	0	0	0	0	0	0