Problem/Motivation

Split from #3391054: Use guzzle async support, and remove batch, for fetching update data

Quoting @drumm:

updates.drupal.org now also responds with compressed responses, if the client uses a Accept-Encoding header.

I believe that will need to be explicitly set with https://docs.guzzlephp.org/en/stable/request-options.html#decode-content

'br',
Our CDN supports both Brotli & gzip. My understanding is that Brotli is better.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

catch created an issue.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

We should send a list of accepted encodings based on what the Drupal site can accept IMHO. I'm proposing a utility class at #3619842: Translation install and update batch does a HEAD and then a GET request for every project unnecessarily for this. Maybe we can reuse that here once that lands? Instead of hardcoding something that may not work. (Currently brotli is not at all a requirement to host Drupal, so I believe if we specify it then get the brotli response, then can't uncompress it, then we were wrong :)