Appliance cloud storage API not handling special characters in object names properly
(Doc ID 2902952.1)
Last updated on OCTOBER 14, 2022
Applies to:
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]Oracle ZFS Storage ZS3-2 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS4-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS5-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
When using the Oracle ZFS Storage Appliance Object API, client systems may report errors such as "Path not supported" or "Not Found". The following may be reported by the database trace logs:
{"code": "NotFound", "message": "Not Found (Path not supported /some/path/to/file%24name)"}
The appliance log file, akOCId.txt, will show errors such as:
zstore.oci.common.errors.OCIError: {"code": "NotFound", "message": "Not Found (Path not supported /some/path/to/bucket/and/file/name)"}
Any special characters will be URL encoded so per the above error, %24 was encoded from the $ symbol (hex code for $ is 24).
Changes
The client may be creating objects with special characters in the name such as !@~#$%^&*()_=-
These special characters are allowed but throw an error and the operation will fail. For reference, the following is the URL encoded mapping for the above characters:
%21 !
%40 @
%7E ~
%23 #
%24 $
%25 %
%5E ^
%26 &
%2A *
%28 (
%29 )
%5F _
%3D =
%2D -
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |