#36293: Extend `django.utils.text.compress_sequence()` to optionally flush data
written to compressed file
-------------------------------+--------------------------------------
Reporter: huoyinghui | Owner: (none)
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: needsinfo
Keywords: gzip flush | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Carlton Gibson):
As per the
[https://docs.djangoproject.com/en/5.1/ref/middleware/#django.middleware.gzip.GZipMiddleware
GZip middleware documentation], response content will not be compressed if
(among other options):
> The response has already set the Content-Encoding header.
You should then be able to set the [https://www.iana.org/assignments/http-
parameters/http-parameters.xhtml#content-coding `identity` content
encoding] before sending the response to bypass the middleware here.
--
Ticket URL: <https://code.djangoproject.com/ticket/36293#comment:7>
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/010701960fd1bb25-694ac575-7d27-4618-9468-ccc00f4693d1-000000%40eu-central-1.amazonses.com.
