Hey Hannes,
Just wanted to follow up on this...
On Tue, Feb 26, 2013 at 2:49 AM, Hannes Schüller <[email protected]> wrote:
> 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.
So is this acceptable to be merged then? The only conflict case remaining
is a local file, in the current directory, with the exact same name as the
domain you'd potentially like to visit. In such case, 'vp2
http://www.example.com' rather than 'vp2 www.example.com' is an easy and
obvious workaround. This seems like reasonable behavior, and I don't see
any other way of handling it short of what you said with actually probing
for a connection or checking DNS.
Regards,
Morgan
------------------------------------------------------------------------------
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
