2049952 - fetch-content should use Accept-Encoding

Status: ASSIGNED

(Firefox Build System :: Task Configuration, task)

Description

[Julien Cristau [:jcristau]]

When migrating the tc artifacts domain to fastly, we hit "503 Response object too large" for large artifacts because of the interaction between gcs's decompressive transcoding (which returns an object with Transfer-Encoding: chunked) and fastly's segmented caching (which uses Range requests under the hood), i.e. if an artifact is stored gzipped in gcs, is larger than 20M (uncompressed), and a client requests that artifact without using Accept-Encoding: gzip, it gets 503. We should ensure fetch-content doesn't run into that (also because it should speed up transfer for those artifacts).

Comment 1

[Julien Cristau [:jcristau]]

Attachment: [taskcluster/taskgraph] fetch-content: send Accept-Encoding header (#992)