Reader Comments

Subscribe: RSS

View by: Time | Thread

• 

  alternatives, 26 Sep 2003 @ 2:31pm

  
  

  huh 'page not found'?

  Why not just put it back to normal and give me back my "page not found" information?
  
  How is 'page not found' correct?
  
  Is it not *MORE* correct to say 'cannot resolve host'? Or how about: whatever.blah.name.com could not be found. Please check the name and try again.
  
  Why ask for more broken behavior of 'page not found'?

  [ link to this | view in chronology ]

  • 

    Mike (profile), 26 Sep 2003 @ 2:35pm

    
    

    Re: huh 'page not found'?

    Hey, okay, now you're just getting into semantics. I just meant the normal informative page if it had trouble finding the host.

    [ link to this | view in chronology ]

  • 

    ::CORY::, 26 Sep 2003 @ 4:27pm

    
    

    Re: huh 'page not found'?

    When you type in a site and it doesnt come up, was the page you wanted found ? No. It doesnt tell you why it wasnt found, spelling, dead server, bad DNS, etc (actually it does if you scroll to the bottom) - just it wasnt found. Which it wasnt.

    [ link to this | view in chronology ]

  • 

    kartar, 26 Sep 2003 @ 4:39pm

    
    

    Re: huh 'page not found'?

    Semantics. It should return the correct NXDOMAIN response as per the RFC.

    [ link to this | view in chronology ]

    • 

      Brandon, 26 Sep 2003 @ 6:21pm

      
      

      Re: huh 'page not found'?

      Hack version 1:
      update your bind server to turn all requests which return the IP address of sitefinder to return NXDOMAIN instead. Restores "correct" behavior. More difficult to implement.
      
      Hack version 2:
      Have a local override for the IP address of sitefinder which actually points at your own service or google. Trivial (I think) to implement.
      
      Personally, I'm still impressed with the number of referrals I've been getting from sitefinder. Currently, its third behind Google and Yahoo.
      
      Brandon

      [ link to this | view in chronology ]

• 

  ::CORY::, 26 Sep 2003 @ 4:38pm

  
  

  To stop this

  (On a windows machine) Find your "hosts" file and add an entry for sitefinder.verisign.com and point it to 127.0.0.1 save and presto, no more verisign page.

  [ link to this | view in chronology ]

  • 

    Anonymous Coward, 26 Sep 2003 @ 6:24pm

    
    

    Re: To stop this

    Great.. now you get cannot connect to server error! :(

    [ link to this | view in chronology ]