Return to New TLD Agreements Forum - Message Thread - FAQ

Username: RayF
Date/Time: Sun, September 16, 2001 at 3:02 PM GMT
Browser: Microsoft Internet Explorer V5.5 using Windows NT 5.0
Subject: Same Problem

Message:
 

 
       
      Yes, I experienced the same problem in attempting to confirm with the Neulevel Registry.  But, let's not get too carried away, they have had only 9+ months to make this operable.  I am sure these glitches must be for our own protection and just another reason we should be thankful for the reserved approach in TLD expansion. I have seen very little go right with these new registries and somehow this has been made to justify the means.  Twisted logic.

Here is the message I received:

Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Ray Fassett
 


Message Thread: