5 ms·
This seems like it is going to cause issues with corporate networks. We use http://search http://search for our internal search portal. My guess is many other c
by nathantotten 14y ago
This seems like it is going to cause issues with corporate networks. We use http://search http://search for our internal search portal. My guess is many other companies do the same. Obviously, the local urls will resolve first, but what happens when browsers and other software expect http://search http://search to conform to a particular api/url pattern?
- TobbenTM 14y agoCurrent browsers search whenever you type anything into the address bar. I don't see any reason to change that and add a cumbersome 'http://search http://search. The http:// http:// should indicate you are not using the browsers search shortcut.
- mh- 14y agothe comment you're replying to is talking about DNS, not a browser keyword.
- ultimoo 14y agoAre you speaking about an api or a url pattern after the response has been received from a uri:search? I believe such information would be set by the responding search server. Also, if this thing kicks off in a good way, there is no reason why internal corporate networks shouldn't start supporting the same api/url as the internet standard.
- Icer5k 14y agoNot only that, but how does ICAAN expect to get around DNS search domains that aren't there by choice, but by default? Almost every ISP I've used has provided a DNS name as part of their DHCP info, and if apex of TLDs start having anything more than NS records, it seems like a lot of things could break until browsers/netadmins/etc. can come up with a fix. Based on how the IPv6 rollout is going, that doesn't inspire confidence...
- TazeTSchnitzel 14y agoI'm just waiting for an appliction for portal. or intranet.