You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given I use https://www.yahoo.com, HtTPs://WwW.YaHoO.cOm or HTTPS://WWW.YAHOO.COM, it would still be resolved to https://www.yahoo.com.
The user tried to type HTTPS://TEST.COM and was given an error by the validator with the default options, even though https is valid by default. With https://TEST.COM, it was no longer failing the validation.
The scheme and host components of a URL are not defined as case-sensitive, but the path and query string are case-sensitive. Typically, the whole URL is specified in lowercase.
the library could lower the case of scheme and host components in order to prevent false negatives.
The text was updated successfully, but these errors were encountered:
Given I use
https://www.yahoo.com
,HtTPs://WwW.YaHoO.cOm
orHTTPS://WWW.YAHOO.COM
, it would still be resolved tohttps://www.yahoo.com
.The user tried to type
HTTPS://TEST.COM
and was given an error by the validator with the default options, even thoughhttps
is valid by default. Withhttps://TEST.COM
, it was no longer failing the validation.Following this article by IBM,
the library could lower the case of scheme and host components in order to prevent false negatives.
The text was updated successfully, but these errors were encountered: