post:// posts:// gets:// etc notification paths are double-encoded

[duozmo]

Describe the bug
If you use a notification path with a space or escape sequence, such as:

• posts://example.com/my endpoint
• posts://example.com/my%20endpoint

Then the notification will be sent to:

posts://example.com/my%2520endpoint

This will likely fail with a 404 or other error, due to the % being encoded as %25.

Version
v0.48.05

How did you install?
Docker Compose

To Reproduce

Steps to reproduce the behavior:

1. Go to notification settings on a watch
2. Set the URL to something with a space or escape sequence, such as posts://example.com/my%20endpoint
3. Push Send test notification
4. Note that notification is not delivered

Example watch: https://changedetection.io/share/0U5lJwB5bmQa

Expected behavior
The notification should be delivered to the supplied path, e.g. my%20endpoint instead of my%2520endpoint.

Desktop (please complete the following information):

• OS: Ubuntu 22.04.3 LTS
• Browser: Vivaldi
• Version 7.0

Additional context
The notification log will show the user-supplied URL (i.e. will not show the problem). This was discovered by wrapping the outbound request in a log statement.

[dgtlmoon]

thanks! is it only posts:// post:// or is it others aswell?

[dgtlmoon]

I reduced the bug to a few lines of code and registered the upstream issue here caronc/apprise#1264

[duozmo]

Perfect, thanks. I'll follow that issue.