Error Pages On Your Website

Bastty

Customer
When a visitor can't access your site, an error page displays.
Each problem is coded. A visitor who enters a nonexistent URL will see 404, while an unauthorized user trying to access a restricted area will see 401.
Web server provides basic error pages (Apache).
You can create a custom error page for any 4 or 5 HTTP status code.
The Error Pages could be:
  • 400 (Bad request)
  • 401 (Authorization required)
  • 402 (Payment required)
  • 403 (Forbidden)
  • 404 (Not found)
  • 405 (Method not allowed)
  • 406 (Not acceptable)
  • 407 (Proxy authentication required)
  • 408 (Request timeout)
  • 409 (Conflict)
  • 410 (Gone)
  • 411 (Length required)
  • 412 (Precondition failed)
  • 413 (Request entity too large)
  • 414 (Request URI too large)
  • 415 (Unsupported media type)
  • 416 (Request range not satisfiable)
  • 417 (Expectation failed)
  • 422 (Unprocessable entity)
  • 423 (Locked)
  • 424 (Failed dependency)
  • 500 (Internal server error)
  • 501 (Not Implemented)
  • 502 (Bad gateway)
  • 503 (Service unavailable)
  • 504 (Gateway timeout)
  • 505 (HTTP version not supported)
  • 506 (Variant also negotiates)
  • 507 (Insufficient storage)
  • 510 (Not extended)
Hope it will help someone.
 
I don't bother creating custom pages for each.

I make usually just three:
* 404 - content not found, might include a search box, might even include some automated 'did you mean' searching
* 503 - site under maintenance with contact details
* everything else - generic error page, might have contact details

Sending a 401 specifically can be weird depending on exactly what you send because this is how you (usually) trigger for the old school Basic authentication popups that you might set up with htaccess.
 
Back
Top