Skip to main content
NetApp Knowledge Base

ONTAP S3 server ignores the range header in GET requests if both the start and ending offsets are not defined

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

Applies to

  • ONTAP S3 Server

Issue

  •  GET requests that include a range header sent to ONTAP S3 server must specify both a start and end offset for the range header to be honored
    • Examples of unhonored ranges would be
      • (5000-) - Bytes 5000 to end of file
      • (-5000) - The last 5000 bytes of the file
    • ONTAP will honor GET requests with range headers that specify both a start and end offset
    • ONTAP will honor GET requests that don't specify a range header
  • If either the start OR the end offset is not specified, the entire object is returned
  • Clients that expect this range to be honored have reported corrupted files when the last offset requested returns the entire file

 

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.