Module 3: Checkpoint summary
All of the requirements and their conformance levels for this module are presented here. This summary can be used as a quick checklist for evaluating web pages.
Checkpoint 1 - Designing URLs
| Conformance: Mandatory |
Agencies must design URLs to last.
Checkpoint 2 - Moving a resource
| Conformance: Mandatory |
When a resource is moved, an appropriate HTTP status message must be presented at the disused URL.
Checkpoint 3 - Removing a resource
| Conformance: Mandatory |
When a resource is removed, an appropriate HTTP status message must be presented at the disused URL.
Checkpoint 4 - Aliasing a resource
| Conformance: Mandatory |
When more than one URL exists for a resource, all alternate URLs must redirect to the primary URL using an appropriate HTTP status message.
Checkpoint 5 - Appropriate use of HTTP methods
| Conformance: Mandatory |
HTTP methods must be used appropriately.
Checkpoint 6 - Handling errors
| Conformance: Desirable |
An appropriate HTTP status message should be presented to the user/agent when an error condition occurs.
Checkpoint 7 - Using best fit statuses
| Conformance: Desirable |
Avoid the use of HTTP statuses 200, 302 or 404 where more appropriate HTTP statuses exist.