Generic worker [already supports](https://docs.taskcluster.net/docs/reference/workers/generic-worker/docs/payload) explicit setting of Content-Type header for task artifacts via optional task property `payload.artifacts[*].contentType`. It should do the same for 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 only support these two options. Existing behaviour to be preserved if property not supplied.
Bug 1536780 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Generic worker [already supports](https://docs.taskcluster.net/docs/reference/workers/generic-worker/docs/payload) 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 only support these two options. Existing behaviour to be preserved if property not supplied.
Generic worker [already supports](https://docs.taskcluster.net/docs/reference/workers/generic-worker/docs/payload) 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.
Generic worker [already supports](https://github.com/taskcluster/generic-worker/blob/52812d990c857adc675b56fa15e5be0bccb9974f/multiuser_windows.yml#L124-L137) 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.