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

Books on Web services security



Web Services Security
Ellen Messmer writes: "For anyone with an interest in XML-based Web Services and the challenge in applying security, this book is an in-depth technical look at access controls, encryption, digital signing, and gateway filtering by Mark O'Neill, chief technology officer at Vordel, with help from six co-authors with computer expertise. More than 300 pages of solidly grounded description of the often-bewilderng alphabet soup of Web Services such as SOAP, UDDI, SAML and WSDL, and clear advice on security approaches as well as a brief overview of privacy-related legal issues." $34.99.


Hits: 15 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.