Skip to main content
NetApp Knowledge Base

ONTAP S3:  cannot set "content-encoding header" to gzip

  1. Last updated
  2. Save as PDF
Views:
255
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9 prior to 9.10
  • ONTAP S3
  • S3 client content-encoding

Issue

  • Cannot set the content encoding in the S3 client to gzip when using the NetApp object store solution, ONTAP S3
  • Setting the content-encoding header in an S3 client returns an error of "not supported". 
  • The following error is seen in S3 Browser log:
    • NotSupported: The header x-amz-copy-source implies functionality that is not supported. 
  •  Packet trace from data LIF shows HTTP 500 Internal Server Error
    • HTTP/1.1 500 Internal Server Error

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.