HTTPServerResponses
From oaibp
Main Page >> Data Provider Implementations
Contents |
[edit] HTTP Server Responses
[edit] Protocol Definition
From the OAI Protocol:
OAI-PMH errors are distinguished from HTTP Status-Codes. Since OAI-PMH uses HTTP as a transport layer, servers implementing OAI-PMH must conform to HTTP status code definitions and report relevant HTTP transport layer status via those Status-Codes. OAI-PMH repositories may employ HTTP Status-Codes in addition to "200 OK".
[edit] Using HTTP Status Headers to Convey the Status of Your Repository
For data providers, it is best practice to supply useful HTTP messages that convey information about the availability of your repository. For HTTP messages used when redirecting to new locations (HTTP 301), load balancing or throttling high traffic rates (HTTP 302), etc., be sure to use the "Location" HTTP field to convey how the service provider should proceed.
[edit] Errors
Most web server applications provide the ability to deliver custom HTTP error messages based on the requests for resources they receive. It is a best practice to make use of these capabilities. Data providers should convey the fullest level of information possible to allow others to determine what the nature of the problem is. Also, it is recommended that data providers share when the repository will be available again for usage.
