-
Notifications
You must be signed in to change notification settings - Fork 71
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
IPv6 URL's not parsed correctly, however IPv4 are #114
Labels
Comments
niftylettuce
added a commit
to spamscanner/spamscanner
that referenced
this issue
Aug 20, 2020
niftylettuce
added a commit
to spamscanner/spamscanner
that referenced
this issue
Aug 21, 2020
github-actions bot
pushed a commit
that referenced
this issue
Jan 23, 2022
# [7.0.0](v6.0.1...v7.0.0) (2022-01-23) ### Bug Fixes * Add support for invalid ipv6 URLs ([b32d16c](b32d16c)), closes [#114](#114) * Remove auto-trimming of input ([4ea86a1](4ea86a1)) ### BREAKING CHANGES * parseDomain won't .trim() the given input. The input is interpreted as it is. If you want to trim the input, you need to call .trim() before passing it to parseDomain. Auto-trimming the input changes the domain and might not be desired if any character (such as whitespace) is allowed (e.g. when using lax validation).
🎉 This issue has been resolved in version 7.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
IPv6 addresses need to be surrounded by I added experimental support for these invalid URLs in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: