Hi Morgan! Morgan Howe <[email protected]> wrote: > 1) Check if it's a search engine > 2) If not a search engine, look for "://", if found, trust the user. > 3) Else, check if it's a file and if so, build the file:// URI > 4) Else, check (again) if it's a search engine > 5) Else, prefix with "http://"; and attempt to open. > > Due to the order of the evaluation, the issue you mentioned originally > should not be a problem.
Actually, this is exactly the main issue I tried explaining initially: the policy change to give precedence to local files over URLs. > Now the only other case would be a file named "http://www.example.com"; > which on any of the systems I have available is not a legal filename > anyway. That would be the one case where the user would need to then > properly specify the file:// prefix, though like I said, I'm not sure > this scenario is even possible. I think we can safely disregard this freak case :) Hannes ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Vimprobable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vimprobable-users
