Inconsistent percent-encoding of keys #13187
Description
My Environment
- ArangoDB Version: 3.7.3
- Storage Engine: RocksDB
- Deployment Mode: Single Server
- Deployment Strategy: Manual Start in Docker
- Configuration: Default
- Infrastructure: own
- Operating System: Ubuntu 20.04
- Total RAM in your machine: 32Gb
- Disks in use: SSD
- Used Package: Docker - official Docker library
Component, Query & Data
Affected feature:
AQL query using web interface
AQL query (if applicable):
insert
{
"_key": "test_%25"
}
into collection_name
Steps to reproduce
- Insert document containing percent-encodable key (e.g.
test_%25) - Attempt retrieval of the document in collection view or through rest api
Problem:
There is inconsistent percent-encoding happening. Documents are inserted correctly as given, but on retrieval are decoded.
I first noticed this problem when searching for a document by key in the collections view. The document was found, but when I click to open it up I get a DocumentNotFoundError. Manually fixing the key encoding in the URL results in the expected document (e.g. .../collection/collection_name/test_%2525)
Expected result:
Encoding (or lack-thereof) is consistent across insert and retrieval