#35354: Simplify ASGIRequest path handling.
-------------------------------------+-------------------------------------
Reporter: Carlton Gibson | Owner: Carlton
Type: | Gibson
Cleanup/optimization | Status: closed
Component: HTTP handling | Version: 5.0
Severity: Normal | Resolution: fixed
Keywords: asgi | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson <carlton.gibson@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"bcd255cd5ca0a1e686d276cca71f45ec400d84a2" bcd255cd]:
{{{#!CommitTicketReference repository=""
revision="bcd255cd5ca0a1e686d276cca71f45ec400d84a2"
Fixed #35354 -- Simplified ASGIRequest path handling.
Following the ASGI HTTP Connection Scope docs[0], the provided `path`
is already the correct value that Django requires.
In combination with `root_path`, from which `script_name` is derived,
the `path_info` variable is set. It's then redundant to
re-calculate `path` from `script_name` and `path_info`.
See also, a clarifying discussion on the ASGIref repo[1].
[0]: https://asgi.readthedocs.io/en/latest/specs/www.html#http-connection-
scope
[1]: https://github.com/django/asgiref/issues/424
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35354#comment:6>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018eafbdfa85-451e10fe-2f76-42d5-9a28-9ee6da1c68d9-000000%40eu-central-1.amazonses.com.
