#36520: Performance Regression in parse_header_params
---------------------------------+------------------------------------
Reporter: David Smith | Owner: (none)
Type: Bug | Status: new
Component: HTTP handling | Version: dev
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Jake Howard):
I'm rather unsure how common parameters are.
Intentionally, probably not especially common. But browses seem eager to
add `charset=utf-8` when they default generate the `Content-Type`. Also,
parameters are used to set the `boundary` for form submissions, so could
be sent with the majority of `POST` requests.
Because any form submission will probably hit the slow path, as could many
other clients, short-circuiting probably isn't the way to go. Given
reverting #35440 ought not to be too complex, we can probably afford to
hold off and see what the response from upstream is.
--
Ticket URL: <https://code.djangoproject.com/ticket/36520#comment:8>
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/010701983cc09bea-ce37fe3b-4d60-420b-ad3f-c76b95207402-000000%40eu-central-1.amazonses.com.
