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 fetched the page http://bibviz.com/ using Lassie, the page has the following og:url setting property="og:url" content="/". Lassie correctly returns the "incorrect" URL.
I wonder if cases like that should be handled by Lassie, i. e. being more forgiving of bad markup, or the calling code. A possibility to handle this in Lassie would be to check that the URL string starts with supported protocols, e. g. http://, https://, and ?.
The text was updated successfully, but these errors were encountered:
I fetched the page http://bibviz.com/ using Lassie, the page has the following og:url setting
property="og:url" content="/"
. Lassie correctly returns the "incorrect" URL.I wonder if cases like that should be handled by Lassie, i. e. being more forgiving of bad markup, or the calling code. A possibility to handle this in Lassie would be to check that the URL string starts with supported protocols, e. g. http://, https://, and ?.
The text was updated successfully, but these errors were encountered: