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.
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.
By Jennifer Mears
Network World, 09/24/01
Standards remain a huge issue for enterprise portals.
XML and its Web services derivatives Universal Description, Discovery
and Integration, and Simple Object Access Protocol are the critical
emerging standards. (See Web
services: Where middleware and XML converge). These
protocols will ensure the portal can incorporate new technologies
as they become available, says Gary Hein, an analyst with The
Burton Group.
Advertisement:
Other standards such as [Security Assertion Markup Language]
will simplify integration between portal and access management
products like Netegrity Siteminder, says Hein. SAML is an
XML security standard for exchanging authentication and authorization
information, currently being developed by the Organization for
the Advancement of Structured Information Standards.
Most vendors claim support for XML, but are waiting for standards such as SOAP
and SAML to be finalized. In lieu, they offer APIs, software developer kits and
third-party add-ins, such as Plumtrees hundreds of Gadgets.
As portal software and XML matures, such proprietary approaches will fade away,
Hein expects. In the meantime, network executives should ensure that code written
to a portals APIs can speak HTTP, as is the case with Gadgets, Plumtree
officials say.
Support for the Lightweight Directory Access Protocol (LDAP) is also critical.
With it, portals can tap into a companys existing LDAP identity and authentication
settings.
Access the latest networking news via your handheld or wireless device! With Fusion Mobile you'll get the day’s top headlines from Network World Fusion.