-
### Environment
Working directory: /home/projects/nuxt-starter-xkjsve 1:20:34 PM
Nuxt project info: …
-
The HTTP input, with sync_response, interprets a `Accept-Encoding: gzip` header as follows.
- A `Content-Encoding: gzip` header is set on the response
- The message is gzipped
See [here](https:…
-
I have some concerns about the complexity of the compression requirements:
>
> 3. The byte array is compressed using DEFLATE [RFC1951] with the
> ZLIB [RFC1950] data format. Implemen…
-
### Is there an existing issue for this?
- [x] I have searched the tracker for existing similar issues and I know that duplicates will be closed
### Describe the Issue
The Accept-Encoding header va…
-
Hello,
I would like to support `Accept-Encoding: gzip` (client) and `Content-Encoding: gzip` (server) so that if the client sets the header, the server will return a compressed json as response and…
-
I'm trying to serve compressed versions of my HTML files. I've added the `-g` flag and I see `Serve GZIP Files: true` during startup. I've zipped a test file using gzip.
- When I try to access the …
-
Because Gzip makes short response larger.
-
### Describe the bug
Streamed Promises work correctly in the development environment (`npm run dev`), but block the page load in a built environment (For example `npm run build && npm run preview`)
…
-
Due to the changes made for the short read functionality using streams which are gzip encoded is massively broken. Accessing the raw response content bypasses gzip decoding and thus the event stream c…
-
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Running `build` command results in:
```
$ v…