> Putting up a dialog with the offending URL giving them the chance to make
> their own decision seems fine to me.
95% of users will say to said dialog "I don't have an %%%% clue", as
Matthew so eloquently pointed out. Users to not know what absolute and
relative URLs are.
> Software can make more than
> reasonable attempts at trying to interpret incomplete information, witness
> typing the root of a domain name and getting http://www.root-domain.com
> . If truth be told I can't really see the downside of interpolating a '/'
> after http:/ but if it is too far a leap of reasoning to let it through let
> the user decide.
The downside is that given:
http:/foo/bar.html
they could have meant the local URI http://foo/bar.html
or the relative uri foo/bar.html. There's no way to tell which.
This is why we have unambigous standards :-)
Gerv
