You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The whitespace seems to be encoded twice. First to %20 and then the % is encoded to %25 which yields %2520. In the end this obviously leads to a 404 on the Vault.
The same behavior can be observed on kv2::read etc.
Here are the relevant logs:
[2023-04-04T20:37:37Z DEBUG rustify::endpoint] Executing endpoint
[2023-04-04T20:37:37Z DEBUG rustify::http] Building endpoint request
[2023-04-04T20:37:37Z DEBUG vaultrs::api] Middleware: prepending v1 version to URL
[2023-04-04T20:37:37Z DEBUG vaultrs::api] Middleware: final URL is https://some-vault-url.com/v1/some%2520secret%2520engine/metadata/some%2520path%2520to%2520a%2520secret
[2023-04-04T20:37:37Z DEBUG vaultrs::api] Middleware: adding token to header
thanks for your work on this library.
The text was updated successfully, but these errors were encountered:
Hi,
I guess I've found a bug when trying to use a path (or the mount) with whitespaces. They seem to be encoded twice.
Example:
will yield the following path: https://some-vault-url.com/v1/some%2520secret%2520engine/metadata/some%2520path%2520to%2520a%2520secret
The whitespace seems to be encoded twice. First to
%20
and then the%
is encoded to%25
which yields%2520
. In the end this obviously leads to a 404 on the Vault.The same behavior can be observed on
kv2::read
etc.Here are the relevant logs:
thanks for your work on this library.
The text was updated successfully, but these errors were encountered: