Skip to main content
NetApp Knowledge Base

CONTAP-419220: ONTAP S3 Requests May Fail Signature Validation with Unencoded Characters

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

Issue

ONTAP S3 requests using Signature Version 2 (SigV2) presigned URLs may fail with SignatureDoesNotMatch when the Signature query parameter contains an unencoded {}/{}. This can occur with clients that do not encode special characters in the signature parameter.

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.