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.

The Bookstore Amazon.com

Storage books



InfiniBand Architecture: Development and Deployment - A Strategic Guide to Server I/O Solutions


Hits: 69 Rating: 0.00 Votes: 0. Rate this resource
Review this resource or submit a comment

iSCSI: The Universal Storage Connection


Hits: 81 Rating: 0.00 Votes: 0. Rate this resource
Review this resource or submit a comment

iSCSI: The Universal Storage Connection


Hits: 80 Rating: 0.00 Votes: 0. Rate this resource
Review this resource or submit a comment

Managing RAID on Linux


Hits: 70 Rating: 0.00 Votes: 0. Rate this resource
Review this resource or submit a comment

Back to top / Back to Bookstore

Error 404--Not Found

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.

Error 404--Not Found

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.