#36483: IntegerField will accept non-ASCII digits, which leads to the same page
appearing at many URLs
-------------------------------------+-------------------------------------
Reporter: Morgan Wahl | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Core (URLs) | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Morgan, could you please provide details of how you are defining your view
and urlconf? There was previous work in #28268 that would ensure that
modern usages of URL definitions would not allow for these fullwidth
unicode digits. So patterns like this:
* `path("something/<int:pk>/", something_detail)`
* `re_path(r"^something/(?P<pk>[0-9]+)/$", something_detail)`
properly raise 404 for non-ascii digits.
--
Ticket URL: <https://code.djangoproject.com/ticket/36483#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070197c24e6664-2af504f5-4ed2-4ae1-b4db-3f90044421fc-000000%40eu-central-1.amazonses.com.
