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.

Internetworking with TCP/IP Level II

Instructor: Dr. Phil Hippensteel

Dr. Phil Hippensteel is a consultant and instructor from Harrisburg, Pennsylvania. He is widely recognized for his knowledge of network infrastructure. His clients include schools, government agencies, hospitals, manufacturing firms, and universities. He has worked with IBM, Sprint, Bethlehem Steel, AMP, Fluke, Mitel, and many other firms throughout the United States and Canada. He has helped to develop networking products and the training associated with those products.

After spending a substantial portion of his career in higher education as professor and college administrator, Dr. Hippensteel began teaching data communications and consulting. He has been an instructor for several major universities and dozens of colleges. He also regularly provides presentations at major conferences and seminars including Supercom, Networld Interop, and the meetings of the International Communications Associations. Recently, he was the keynote speaker for a seminar series conducted nation-wide by Network World magazine.

To bring this course on-site, please call Michele Zarella at 508.490.6620 or email at mzarella@nww.com
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.