-
Notifications
You must be signed in to change notification settings - Fork 1
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
Evaluate URLs enclosed within angle brackets as URLs #246
Comments
atc0005
added a commit
that referenced
this issue
Mar 27, 2024
Match URLs enclosed within angle brackets as URL patterns, removing them before parsing and further evaluation as potential Safe Links URLs. refs GH-246
As of v0.5.0-alpha.15 this functionality is not present in either of:
|
atc0005
added a commit
that referenced
this issue
Apr 8, 2024
- cmd/usl - small refactor to move all URL cleaning behavior from `ReadURLsFromInput` to `ProcessInputURLs` - add debug logging toggle to `main` func (disabled by default) - fix logic bug with `safelinks.ValidSafeLinkURL` check - cmd/dsl - small refactor to `processInput` func to reuse logic from `safelinks.DecodeInput` (functionality and test coverage) refs GH-246
atc0005
added a commit
that referenced
this issue
Apr 10, 2024
Match URLs enclosed within angle brackets as URL patterns, removing them before parsing and further evaluation as potential Safe Links URLs. Remove double-cleaning of inputURL left over from earlier refactor work on cmd/usl to "pull back" functionality from the safelinks package. refs GH-246
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
When evaluating release v0.5.0-alpha.5 with some test input emails I noticed that it failed to recognize URLs wrapped in angle brackets as URLs.
Some light digging later I learned that wrapping URLs in angle brackets is a common practice with Outlook to prevent splitting of URLs across lines. All current tools should be updated to consider URLs wrapped within angle brackets as URLs and then strip them before parsing.
References
The text was updated successfully, but these errors were encountered: