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
33365	Functionality change in 3.2.10 for re_path().	Pkt	nobody	"3.2.10 does the following change in urls/resolvers.conf:

out:
{{{
        match = self.regex.search(path)
}}}

in:
{{{
        match = (
            self.regex.fullmatch(path)
            if self._is_endpoint and self.regex.pattern.endswith('$')
            else self.regex.search(path)
        )
}}}

Now, that's a big change, because I have an endpoint that is now giving 404s:

{{{
    re_path(r""validate$"", ValidateView.as_view(), name=""validate""),
}}}

The error is assuming that just because it ends in ''$'', it has to use fullmatch. I'm using (was using) that to catch ''/*whatever*/validate'' urls.

It is a big enough change that it should at least have been noted explicitly in the release notes. And, IMHO, it's a mistake (I'll admit to not having read the CVE that prompted this change)."	Bug	closed	Core (URLs)	3.2	Normal	invalid	3.2.10 resolvers re_path	Florian Apolloner	Unreviewed	0	0	0	0	0	0