-
Notifications
You must be signed in to change notification settings - Fork 940
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storage pool used by is double url encoded #12398
Labels
Bug
Confirmed to be a bug
Comments
tomponline
added a commit
to tomponline/lxd
that referenced
this issue
Oct 18, 2023
Go's net.URL requires Path to be populated with unencoded path and RawPath to be populated with the hint on how we want Path to be encoded. This avoids double path encoding when calling url.EscapedPath(), which is used in url.String(). Fixes canonical#12398 Signed-off-by: Thomas Parrott <[email protected]>
tomponline
added a commit
to tomponline/lxd
that referenced
this issue
Oct 18, 2023
Go's net.URL requires Path to be populated with unencoded path and RawPath to be populated with the hint on how we want Path to be encoded. This avoids double path encoding when calling url.EscapedPath(), which is used in url.String(). Fixes canonical#12398 Signed-off-by: Thomas Parrott <[email protected]>
tomponline
added a commit
to tomponline/lxd
that referenced
this issue
Dec 5, 2023
Go's net.URL requires Path to be populated with unencoded path and RawPath to be populated with the hint on how we want Path to be encoded. This avoids double path encoding when calling url.EscapedPath(), which is used in url.String(). Fixes canonical#12398 Signed-off-by: Thomas Parrott <[email protected]>
tomponline
added a commit
to tomponline/lxd
that referenced
this issue
Dec 5, 2023
Go's net.URL requires Path to be populated with unencoded path and RawPath to be populated with the hint on how we want Path to be encoded. This avoids double path encoding when calling url.EscapedPath(), which is used in url.String(). Fixes canonical#12398 Signed-off-by: Thomas Parrott <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required information
Issue description
In directory storage pools, non-ascii characters are allowed in custom volume names. The storage pools used_by section url encodes those names twice, resulting in broken urls.
Steps to reproduce
dir
with driver directorytüdeldü
.GET 1.0/storage-pools/dir
(see screenshot below)The returned url is
But the correct url is
Appearently the volume name is url encoded twice. It should only be encoded once.
The text was updated successfully, but these errors were encountered: