----------------------------Original message---------------------------- ---------------------------- Forwarded with Changes --------------------------- >From: [log in to unmask] at @UCSD >Date: 11/23/97 11:33PM >To: larry cruse at UCSDLIBRARY >Subject: Monitor: Error on geographic names information system ------------------------------------------------------------------------------- does anyone have a url for these? HTTP Error Codes 2xx Success! 200 OK - normal completion of request 201 202 _ These are very rare under our setup 203 / and can be ignored. 204 / 3xx Redirection 301 Moved. This file has permanently moved, and our records should be updated to reflect the new URI. 302 Found. The remote server is issuing a "redirect" to point us towards another URI, but we should keep this original URI in our files. This is often used for Imagemap and "jump to random link" features. 303 Method. We shouldn't see this, as this status code has not been formally approved. 304 Not modified. A client can request that a remote URI be sent only if has been modified since a certain date. This response means that the URI exists but does not meet the date criterion. 4xx Error in Request 400 Bad syntax in request, perhaps due to an error in our software, but more likely a broken server on the remote system. 401 Unauthorized. 402 Payment required. 403 Forbidden. This is probably due to improper file permissions on remote files. 404 Not found. This is a true "broken link" and needs to be fixed in our HTML files. 5xx Server Error 500 Internal server error on the remote system. 501 Not implemented. This error could point to a problem on either system, or even in the URI we're trying to access. 502 Server temporarily overloaded. Some newer servers issue this "busy signal" which instructs clients to try their request again at a later time. 503 Gateway timeout. We should never see this, since we're not using a proxy server. 6xx Client Error 600 The client could not decipher the requested URI. This might point to an error in the URI or to an error in Monitor itself. 601 Not implemented in client. Monitor only knows how to process "http://" requests; other methods will not be tested. 602 Connection failed. The initial connection to the remote system failed. This probably means that the other site is either down, busy, or unreachable from our network. 603 Timed out. The initial connection was successful, but the remote server took too long servicing our request. Monitor may wait five minutes before aborting. This indicates a busy or malfunctioning remote server. u>