The Content-Encoding header is not currently supported, but will be in the future. The future implementation will likely just store the encoding type that is specified during upload. Once this value is stored it will be returned with the that file through hosted, download token, or session token downloads...