How to handle wrong URL setting

[yaph]

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 ?.

[michaelhelmick]

If the content doesn't start with http(s), I think we can allow lassie to be more forgiving and just use the url that the user is requesting.