Generic worker already supports explicit setting of HTTP Content-Type header for task artifacts via optional task property payload.artifacts[*].contentType.

It should do the same for HTTP Content-Encoding header via optional task property payload.artifacts[*].contentEncoding.

This would allow a task author to explicitly set Content-Encoding to either identity or gzip.

I propose we support only these two values.

Existing behaviour to be preserved if property not supplied.

can I work on this bug?

Sure, Vaibhav.

Source code is available at https://github.com/taskcluster/generic-worker.

Let me know if you have questions.

Note, the link in comment 0 is no longer valid, but the payload schemas can be seen in raw here:

https://github.com/taskcluster/generic-worker/blob/v14.1.0/native_all-unix-style.yml#L107-L121 (mac, linux)
https://github.com/taskcluster/generic-worker/blob/v14.1.0/native_windows.yml#L111-L124 (windows)

Hi Vaibhav, are you still working on this?

Many thanks,
Pete

Yes Pete, I am back on track & working on it again

Thanks Vaibhav!

https://github.com/taskcluster/generic-worker/commit/52812d990c857adc675b56fa15e5be0bccb9974f

Released in generic-worker 16.2.0.

Note: testing on gecko Windows worker types in this try push.