Back to Object Storage FAQs
HELP CENTER · FAQObject Storage2 min read

Why are object storage keys containing ../ rejected?

IaGenify rejects object storage keys that contain a path segment equal to `.` or `..`. These segments can make a key appear to escape its intended location, so the storage API treats them as invalid instead of accepting an ambiguous path.

Object Storage

Keys identify objects inside a storage

An object storage key is the name used to locate an object within the selected storage. It is not a command to navigate a local folder tree. IaGenify treats keys as relative to the storage and refuses a segment that is exactly `.` or `..`, returning an invalid-key error.

A slash can still separate parts of a key, and a key ending with `/` can represent a folder marker. The safety check concerns traversal segments, not ordinary nested names such as `reports/2026/january.csv`. Keep the intended hierarchy in the key while avoiding dot segments that could be interpreted as moving upward.

Correct the key before retrying

When an upload or lookup is rejected, inspect the exact key string, including any prefix added by a workflow or application. Remove path traversal components and construct the key from known, validated segments. Do not try alternate encodings to bypass the rejection; use a clear relative key inside the intended storage.

A rejected key does not mean the object was partly uploaded. Once you correct it, verify the object using the same storage and key before using it in a later workflow step. For deletion, double-check the complete key because removing an object permanently deletes its data.

Back to Object Storage FAQs