Closed MikeGoldsmith closed 3 months ago
There is a weird bug in setting a URL path directly, where it will escape some characters, but not all.
This go playground example shows it. The unescaped value is used directly, the escaped value double escapes some of the characters.
This PR uses url.PathJoin instead, which is intended to handle URLs.
Which problem is this PR solving?
There is a weird bug in setting a URL path directly, where it will escape some characters, but not all.
This go playground example shows it. The unescaped value is used directly, the escaped value double escapes some of the characters.
This PR uses url.PathJoin instead, which is intended to handle URLs.
Short description of the changes