Hi bob3160,
But read here why Google wants to get rid of the uri, but does not really know what to trade it for.
Will this all mean more security through obscurity? Read:
https://arstechnica.com/gadgets/2018/09/google-wants-to-get-rid-of-urls-but-doesnt-know-what-to-use-instead/They hope that obscuring the uri will keep malcreants, that exploit uri's, at bay, and others will no longer feel alarmed,
but it is Google's very mono-culture, ubiquity and complexity that sets it out as an ideal target for malcreants.
That's the real eliphant in the room, no one likes to see or discuss.
See the example given here: This is how a Chrome 57 displays
https://www.xn--80ak6aa92e.com/.
Note the
https://www.apple.com in the address bar.
Hey there!
This site is obviously not affiliated with Apple, but rather a demonstration of a flaw in the way unicode domains are handled in browsers. It is very possible that your browser isn't affected.
Test it out inside the new Google Chrome version "without www and https://*/* and http://*/* in the search bar".
From Google we do not hear a word for what they plan with uri's for the future, deafening silence there.
In the mean time check with this tool to have a grip on the dangers:
https://www.duplichecker.com/url-rewriting-tool.phppolonus (volunteer 3rd party cold reconnaissance website security analyst and website error-hunter)