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

LAN books



Gigabit Ethernet : Technology and Applications for High-Speed LANs


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

Internetworking with TCP/IP Vol. II: ANSI C Version: Design, Implementation, and


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

Internetworking with TCP/IP Vol.1: Principles, Protocols, and Architecture (4th Edition)


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

Internetworking with TCP/IP, Vol. III: Client-Server Programming and Applications


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

OSPF Complete Implementation (With CD-ROM)
"This book is the companion to OSPF: Anatomy of an Internet Routing Protocol. In keeping with the Internet tradition of valuing "rough consensus and working code," this book provides a complete OSPF implementation to go with the previous description of the OSPF protocol. The implementation is written in C++ and has been designed for portability. Two sample ports are included: (1) an OSPF routing daemon, called ospfd, for the Linux operating system and (2) an OSPF routing simulator, ospf_sim, that can be run under Linux or Windows.

The text of this book provides design documentation for the implementation, a porting guide, and user manuals for the two sample ports. The data flow and major data structures are explained, using code fragments when necessary. The complete implementation is contained in an attached CD-ROM." $54.95



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

OSPF: Anatomy of An Internet Routing Protocol
"A methodical and detailed description of the protocol is offered and OSPF's role within the wider context of a TCP/IP network is demonstrated.

Practical throughout, the book provides not only a theoretical description of Internet routing, but also a real-world look into how theory translates into practice. It shows how algorithms are implemented, and how the routing protocols function in a working network where transmission lines and routers routinely break down.

You will find clear explanations of such routing fundamentals as how a router forwards packets, IP addressing, CIDR (Classless Inter-Domain Routing), the routing table, Internet routing architecture, and the two main routing technologies: Distance Vector and link-state algorithms."

$49.99.


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