On Wed, 17 Sep 2003, Alex Kamantauskas wrote:
Not really operational content, but I was wondering if there was an
intellectual property issue with the Verisign .com/.net redirect?
For instance, http://searchthewebwithgoogle.com/ brings you to a
Verisign search engine.
Or, even
Not really operational content, but I was wondering if there was an
intellectual property issue with the Verisign .com/.net redirect?
For instance, http://searchthewebwithgoogle.com/ brings you to a
Verisign search engine.
Or, even better, http://getyourdomainnameatregister.com/ will
Alex Kamantauskas wrote:
Not really operational content, but I was wondering if there was an
intellectual property issue with the Verisign .com/.net redirect?
Not sure about IP, but there are privacy issues. Verisign has
intentionally redirected all email that was mistyped on the recipient to
On Wed, 17 Sep 2003, Jack Bates wrote:
Not sure about IP, but there are privacy issues. Verisign has
intentionally redirected all email that was mistyped on the recipient to
their server. Instead of immediately rejecting and terminating the
connection, they allow the send to issue 3
On Wed, 17 Sep 2003 19:39 (UTC) Len Sassaman [EMAIL PROTECTED] wrote:
| As Microsoft's features are client-side, no user information
| is leaked without the user's knowledge.
Do you have any form of evidence to support that proposition?
s/is/should be/ and I might have been with you ... ;-)
|
On Wed, 17 Sep 2003, Richard Cox wrote:
Do you have any form of evidence to support that proposition?
s/is/should be/ and I might have been with you ... ;-)
Well, things may have changed since I looked at it, but I recall that not
too long ago, a mistyped domain name resulted in a local page
On Wed, 17 Sep 2003, Len Sassaman wrote:
Are users now redirected to Microsoft automatically?
I just checked this again, and in fact I was incorrect -- the requested
URL is passed to search.msn.com. That's unfortunate.
(Our proxies return their own site not found page, so our users won't
