Prevent notification attachments failing due to spaces ( ) in url #3930
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dshokouhi
approved these changes
Oct 11, 2023
JBassett
approved these changes
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix #3926 by automatically replacing
%20. Not replacing any other characters as that might break URLs including already encoded URLs. (This feels like a 'safe' change to automatically handle common user errors.)Without this change, a notification attachment containing a space will fail the URL validation. Because of that failure it returns the base URL and downloads it (= the login page), which then cannot be processed as an image/video.
Screenshots
n/a
Link to pull request in Documentation repository
n/a
Any other notes