Domain: intranet
Stories and comments across the archive that link to intranet.
Comments · 8
-
Re:http://apple
That's a valid URL, for internal to your own DNS server. If no FQDN is provided pointing it to a domain outside your own, it will try to match up that name to any A records or CNAME records that exist on your DNS.
Many organizations do this for internal webpages. http://intranet/ , http://learning/ , http://getservice/ are examples of how some companies do this. It's not the same as the Google suggestion, which is making a top level FQDN domain.
-
Re:Finally looks exactly like Chrome
After all, who's to say you didn't really intend https://intranet/ [intranet]?
Or, for that matter, mailto:intranet ?
-
Re:Finally looks exactly like Chrome
ooh! I know, the user is wanting to search for those on google!!
I entered both of those URLs along with an IP which is actually accessible to me into three different browsers (Chrome, Opera, and Firefox for Linux), and not once did I get a search. Opera and Firefox did add an explicit
.com at the end of http://intranet/ and went to http://www.intranet.com./I also tried just the IP addresses without the http:/// prefix, and not one of them led to a search page.
The only thing that did was entering "intranet" on its own. But turning on troll mode (though "troll mode with a point") for a second, that's not a URL; http://intranet/ is the URL. Your browser is already applying a heruistic (prefix the scheme) to arrive at the URL. After all, who's to say you didn't really intend https://intranet/? In some sense, all the browsers are doing in that case is applying a different heuristic that goes to a far less related page.
-
Re:Finally looks exactly like Chrome
ooh! I know, the user is wanting to search for those on google!!
I entered both of those URLs along with an IP which is actually accessible to me into three different browsers (Chrome, Opera, and Firefox for Linux), and not once did I get a search. Opera and Firefox did add an explicit
.com at the end of http://intranet/ and went to http://www.intranet.com./I also tried just the IP addresses without the http:/// prefix, and not one of them led to a search page.
The only thing that did was entering "intranet" on its own. But turning on troll mode (though "troll mode with a point") for a second, that's not a URL; http://intranet/ is the URL. Your browser is already applying a heruistic (prefix the scheme) to arrive at the URL. After all, who's to say you didn't really intend https://intranet/? In some sense, all the browsers are doing in that case is applying a different heuristic that goes to a far less related page.
-
Re:Finally looks exactly like Chrome
ooh! I know, the user is wanting to search for those on google!!
I entered both of those URLs along with an IP which is actually accessible to me into three different browsers (Chrome, Opera, and Firefox for Linux), and not once did I get a search. Opera and Firefox did add an explicit
.com at the end of http://intranet/ and went to http://www.intranet.com./I also tried just the IP addresses without the http:/// prefix, and not one of them led to a search page.
The only thing that did was entering "intranet" on its own. But turning on troll mode (though "troll mode with a point") for a second, that's not a URL; http://intranet/ is the URL. Your browser is already applying a heruistic (prefix the scheme) to arrive at the URL. After all, who's to say you didn't really intend https://intranet/? In some sense, all the browsers are doing in that case is applying a different heuristic that goes to a far less related page.
-
Re:Misleading summary.... it's INTRANET ONLY
Ok, what about http://intranet/ ? Obviously the local domain controller is handling things there; shops with intranets that only work in IE6 are almost certainly using an MS-based server.
I just opened up the IE8 beta in a VM, and went to 192.168.0.11 (my OS X webserver's local address) and it doesn't detect automatically as Intranet. It also misses my router at 192.168.0.1, however it does get the WAMP install at http://localhost/ unsurprisingly. Doubleclicking the internet icon in the bottom to check the sites has:
(X) Automatically detect intranet network
-- (X) Include all local (intranet) sites not listed in other zones
-- (X) Include all sites that bypass the proxy server
-- (X) Include all network paths (UNC)You can also go advanced from there and add in additional sites by address or IP.
So I have no idea how it handles the detection. It doesn't do a great job, but then interestingly enough it doesn't consistently give the option to use the compatibility view either. It doesn't appear to be based off of the doctype, availability of IE-only stylesheets, intra/extra/internet location, or anything else that would make sense from my brief testing.
-
Re:Authentication - the major obstacle
Presumably you mean SPNEGO? It's designed as a sort of extension to NTLM auth (using Kerberos instead) and is quite common inside MS shops using AD and almost any using SharePoint.
FF has a fix for it though, in about:config filter for NTLM and look for "network.automatic-ntlm-auth.trusted-uris" - enter the base URL for your intranet servers and/or proxies (e.g. for https://intranet/ you'd just add "intranet") and the problem should go away. Wish Opera supported SPNEGO though :(
Hope I'm not barkin gup the wrong tree, not found any auth methods that FF couldn't handle without some finagling. -
Interesting Slashdotting defense
http://web.archive.org/bountyquest.com/patentinfo
/ oneclickart.htm now has a 301 redirect to http://intranet/