-
Should have a way to decode Response Bodies if a **Content-Encoding** Header is present and set as _gzip/deflate_
-
It looks like https://github.com/dakrone/clj-http/blob/3.x/src/clj_http/util.clj#L45 and https://github.com/dakrone/clj-http/blob/3.x/src/clj_http/util.clj#L99 are leaking connections - the input stre…
-
BUG? Dolibarr v20 says no compression on HTTP responses enabled
```
Files of type php (.php) are not compressed by HTTP server
Files of type css (.css) are not compressed by HTTP server
Files…
-
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior
When I send a GET request with header `accept-encoding: gzip, deflate` I expect the response …
-
To reduce request size, often the body is compressed. A mechanism that supports this is currently missing from Wisp.
I am not quite sure what scope of a solution is a good fit for Wisp. A full flow…
ofekd updated
2 weeks ago
-
On Apache, ModSecurity's response body scanning can conflict with `mod_deflate`.
If the response body is compressed by `mod_deflate`, it's possible that ModSecurity scans the _compressed_ response, i…
-
Websocket streams operating in client mode need to check the offer returned by the server to verify that it meets the criteria, otherwise the handshake function should return an error.
-
# Issue
As highlighted in #6330, the deflate content encoding used in HTTP responses by `osrm-routed` is broken.
This bug is obscured by most browsers/clients accepting gzip and deflate, with the …
-
### Detailed Description of the Problem
I checked that even if I enabled the option, I got an error response.
It seems that the intention is to leave only log on the code.
```
…