Comment #4 on issue 5434 by joseph.odoherty: //url.tld resolves to file://url.tld rather than http://url.tld http://code.google.com/p/chromium/issues/detail?id=5434
This is strange given the behavior of the other major browsers. What is the rationale for this design? Surely one can suppose that users generally intend to use their browser for accessing resources on web servers more often than accessing local resources. And if so, it makes sense to interpret malformed URIs as being for the http scheme rather than the file scheme. P(http|missing_scheme) > P(file|missing_scheme) Are //foo.bar or //foo/bar valid URIs or ECU paths and I am just not aware of it? As far as I can tell "//" is not a valid path specifier except for on the Domain/OS-- a platform that I don't believe Chromium targets. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
