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
I think we need to change the regexps so that there's regexp that just finds the tags and calls a callback method for determining the details. In most cases, we need to find only the opening tag -- with the exception of some special ones such as code block and script/style tag.
I did add the whitespace check but it doesn't fully resolve the problem. It just allows a way around the issue of a false positive.
Checking inside HTML tags is not trivial as it will basically require the use of a parser to accurately determine the scope of the tags. The other downside is that it will be MUCH slower than the regex alone.
If in your content you have a legitimate text that includes a protocol, it gets flagged as false-positive. Example:
This triggers
invalid_protocols
, caused by the defaultdata
protocol valueOne solution is to ensure the protocol is followed by at least one non-space character. If there is a space, it should be ignored.
The text was updated successfully, but these errors were encountered: