- π¦πΉAustria torotil
I donβt think this will lead to a change in Drupal 7 at this point, but actually the reason cited here is wrong. The HTTP specs say:
If no Accept-Encoding header field is in the request, any content coding is considered acceptable by the user agent.
β https://www.rfc-editor.org/rfc/rfc9110.html#section-12.5.3-10.1
Users can work around this by either explicitly specifying
Accept-Encoding: identity
or by handling theContent-Encoding
header as is shown here: https://drupal.stackexchange.com/a/136774