Apache ошибка 501

Error 400: Bad Request

If an HTTP request completely fails to adhere to the HTTP protocol, the web server may classify it as being abnormal and serve a 400 error page. This error shows that the request was not in a format that the server recognized.

This error is primarily an error in programming, either on the client or the server.

Error 401: Authorization Required (Unauthorized)

When encountering a 401: Authorization Required error it means that you simply entered the password incorrectly on a server login form. If you no longer remember the username and password, you can reset it by following the steps listed in this article.

Below is what a common 401 page looks like.

But do keep in mind that 401 pages can look very different from site to site.

For more information about Error 401, please see this Wikipedia article.

Error 403: Forbidden

While using the internet, you may run into an Error 403 – Forbidden page. This page appears when you don’t have access to the page you are trying to view. This can be caused by a few things, below we will cover the most common.

• The folder you are trying to access does not have a index page and has indexing turned off.
  • You can check this in more detail by reading this article.
• An incorrectly configured htaccess file
• The file has incorrect permissions set (USER does not have read permissions).
  • You can look into this by following the steps in this article.

You can also check the error logs to attempt to get more details. For information on how to check the error logs.

Below is what a common 403 page looks like.

But do keep in mind that 403 pages can look very different from site to site.

For more information about Error 403, please see this Wikipedia article.

Error 404: Page Not Found

While using the internet, you may run into a 404: Page Not Found error. This means that you are accessing a page that does not exist. In most situations, its because the link that took you to the page was not updated to reflect a new file location. Below we will outline a few things you may want to check if you are seeing this error on your website.

Please keep in mind that links are cAsE-SenSiTive

• If you are using a flat html website (not using a sript/application like wordpress). we recomend that you use FTP or the file manager to check if the file you are attempting to access is in the correct location.
• If you are using a script/application like WordPress, you may want to make sure that the page is published and the link you are attempting to use is correct.
• If the page was working before, you may want to check to see if other pages are affected. If they are, you may have a site wide issue such as a bad update for a script/software, incorrect use of redirects, etc.

Note: In some cases you may be redirected away from the original link to the home page, or another error page. Keep this in mind when debugging the issue.

Below is what a common 404 page looks like.

But do keep in mind that 404 pages can look very different from site to site.

For more information about Error 404, please see this Wikipedia article.

Error 405: Method Not Allowed

The 405 error page seldom occurs as it explicitly shows that the mail user agent(email client) in use is attempting to access the server via a restricted method. The error would show a problem with the client software.

Error 406: Not Acceptable

A 406 error occurs when the server is unable to accommodate a request for data in a specific format. However, most browsers accept any data received from the server. If you encounter this error, contact the software’s technical support for assistance.

Error 407: Proxy Authentication Required

A 407 error, similar to a 401 error, is a problem with authentication. The distinction is basically in how the server expects the authentication. While a server generating a 401 error requires direct authentication, a 407 error occurs when an authentication is required via a proxy.

Error 408: Request Time-Out

This error occurs when the server disconnects you from the client due to a long time has passed between the initial connection and the transfer of data.

Several possible issues can cause this problem, including a high load on the client matching, problems with your local area network, problems with your ISP, difficulties with the route to the server, and ultimately it could be caused by a high load on the server.

If you encounter this error, run a traceroute for any issues or delays:

How do I perform a traceroute?

Error 409: Conflicting Request

When a call to the server conflicts a set rule, the server may cause a 409 error to show that two requests conflict with one another. This issue is almost never caused by standard web server authority or security as those methods produce different errors. A 409 error page normally needs an application specific issue that is not defined by the HTTP protocol.

Error 410: Gone

A 410 error page, similar to a 404 error page, can sometimes be generated to indicate that the data requested is not available.  The primary difference between the two errors is that a 410 error page generates additional information to show that the data previously existed but is no longer available.  If a server has no process for recognizing if data previously existed, then a 404 error page is served.

Error 411: Content Length Required

The server may need a length of data to be specified when using HTTP protocols that require storing data on a server, such as PUT or POST.  If the length of data needs to be specified by the server and the request fails to define the length of data, the server returns a 411 error.

Error 412: Precondition Failed

If a browser or client, sending an HTTP data stream to the server, can incorporate specs for the data stream, this functionality is referred to as a precondition. If a precondition is required, but not satisfied, the server generates a 412 error.

This issue can only occur when a client-side application does not satisfy a spec set by itself, diagnose this issue as a problem with the client and identify the precondition that is not satisfied.

Error 413: Payload Too Large (Request Entity Too Large)

The 413 error code means that the server is rejecting a call since the request data stream is larger than the server is willing or able to process. What is or is not “too large” is contingent on the call the client is making and the restriction set on the server. The server might close the connection to deter the client from continuing the request.

If the issue is temporary, the server should generate a
Retry-After header field to show that the issue is temporary and when the client may try again.

Error 414: URI Too Long (Request-URI Too Long)

The 414 error page is triggered when the URL is set up in a way that successfully reaches the server, however, is too long for the server to interpret due to server constraints.

If you encounter this error, recode the website to utilize a shorter URL.

Error 415: Unsupported Media Type

When a browser or client uses an HTTP protocol to transfer data to the server, the server may require specifying the media type transmitted. A 415 error occurs when any of the following conditions are met:

• The specified media type does not match the original media included in the request.
• The original media provided in the request is conflicting with the current resource data.
• The original media included is conflicting with the method specified in the HTTP request.

The majority of users do not encounter this error as it is a characteristic of programming issues with a specific feature, and needs development to fix.

Troubleshooting this issue requires you to analyze the media type that your client is trying to transfer via HTTP, and what kind of media type the request is claiming to send, and the expected media type by the server.

Error 421: Too Many Connections

The highest number of connections allowed from one IP is 8 for shared and reseller servers, if you experience a 421 error, this indicates that you have exceeded the max connections allowed. Additionally, you can no longer control your FTP connections via FTP Connections in SiteAdmin or cPanel; you must manage the FTP session via your FTP client.  For more information on managing FTP sessions, please review the article below.

FTP: Create and manage additional FTP accounts

Error 500: Internal Server Error

At some point, you may run into an error page that reads Internal Server Error or Error 500. This is whats known as a server error and can be caused by a large number of things. Below we have outlined some of the most common ones.

• CHMOD is set to 777
  • For security reasons, we don’t allow permissions of 777. When you attempt to use this permission type, the page will display a internal server error. For more information about this, please see our CHMOD article.
• A incorrectly configured htaccess file.
  • htaccess files are very powerful, but in turn when incorrectly used or configured, can cause errors. You can attempt to disable or comment out parts of the htaccess file to see what line is causing the issue.
  • One of the most common htaccess issues that would cause a internal server error is attempting to use php_flag. We don’t support the use of php_flags on our servers. Any custom php changes should be made through a .user.ini file.

There are a number of other reasons that may cause this error. Checking the error log is a good way of starting to narrow down the problem. For information on how to check the error logs.

Below is what a common 500 error looks like.

But do keep in mind that 500 errors can look very different from site to site.

Error 501: Not Implemented

This error message is usually due to a problem with the browser or client used to access the server. The error message means that the HTTP method utilized by the browser or client is not supported or recognized by the server. Also, the methods currently specified by the HTTP protocol are as follows: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, and CONNECT.

Error 502: Bad Gateway

This error message can generate in various forms(HTTP 502, Temporary Error (502), 502 Service quickly Overloaded,  and 502 Proxy Error). This error message occurs when one server receives an invalid response from another server that is trying to load a website or execute another request. The problem is often a network issue between servers on the internet.  You can take some measures to alleviate the issue such as use a different browser to load the site, refresh the page, start a new browsing session, or clear your browser cache.

Error 503: Service Unavailable

This status code usually occurs when your server is undergoing maintenance or temporarily overloaded. A 503 error lets visitors know that, although the service or data is temporarily not available, the website still exists.

Error 504: Gateway Timeout

When attempting to access a website and a response is not provided after a certain amount of time, a 504 error page may appear in your browser. 504 errors are usually the result of trying to reach a server that is either undergoing maintenance or not correctly functioning.

Error 505: HTTP Version Not Supported

If a client uses a version of the HTTP protocol that is no longer supported by the server, a 505 occurs. This error is rare and using a client that uses the current HTTP protocol standards resolves the issue.

Account Suspension

An encounter with the Account Suspended page is a strong indicator of some concerns with the account to which the website is linked. When an account is suspended, traffic to all the websites on the particular cPanel account in question are redirected to a generic account suspension page. When the account is then unsuspended, this redirect will be removed automatically.

The first cause of the suspension typically occurs when an account reaches delinquent billing status. If you are the account holder, you can review any outstanding invoices by logging into your BloxPortal (https://www.snapblox.com/portal). While logged into BloxPortal as the account holder, you can also update the payment information and pay payment for any outstanding invoices. After all outstanding invoices have been cleared up, your hosting will be unsuspended and your website(s) will return to full functionality.

If you encounter the suspended page, and your account is fully up to date in regards to billing, the suspension may be attributed to resource usage on your website. Depending on the type of hosting plan you have with us, you may have limits on how many shared (CPU, Memory, etc) resources you may use. If your account is found using to many of the shared resources our team will contact you via a ticket.For more information on the resource usage, you can check the resources overview section of our knowledgebase.

In the event you encounter the suspended page and your account is in good standing, please check your email messages or BloxPortal for communication from our staff. If you do not have any communication from our staff, please get in touch with us and we will investigate right away.

I was trying to find an official, authoritative list of HTTP Status Codes but I kept finding lists that weren’t authoritative or complete. So I searched and found my answer in the Apache HTTP Server source code. Once I had the exact HTTP Status Codes and resulting Error Documents sent by Apache, I researched deeper into HTTP Status Codes by reading as many related RFC’s as I could find, and several other software source codes were explored. This is the most authoritative list I know of, if you can do better leave a comment and I’ll update it. Another thing to keep in mind, the Status code number itself is what is used by software and hardware to make determinations, the phrase returned by the status code is for the human only and does not have any weight other than informing the user.. So «503 Service Unavailable», «503 Service Temporarily Unavailable», and «503 Get the heck outta here» are all completely valid.

Update March 9, 2009: A lot of sites on the web have updated their HTTP status code lists to include the HTTP Status codes listed on this page, including Wikipedia, IANA, W3C, and others, so rest assured this info is accurate and complete. If you’d like to see how to create custom error pages for all of these errors like mine /show-error-506 , then check out this detailed tutorial I just posted.

57 APACHE HTTP STATUS RESPONSE CODES

Once I compiled the list of Apache recognized HTTP Status Codes, I was dying to see them all in action (i.e. the corresponding ErrorDocument). At first I thought I would have to create a php or perl script emulating each of the 57 HTTP Status Codes, a tedious undertaking I wasn’t about to do. Instead I «asked Apache» by searching the Apache HTTP Documentation for ambiguity sending Status Codes and/or triggering ErrorDocuments with an Apache Directive.
While reading up on mod_alias and the Redirect directive I found:

Apache Docs

Syntax: Redirect [status] URL-path URL The status argument can be used to return other HTTP status codes. Other status codes can be returned by giving the numeric status code as the value of status. If the status is between 300 and 399, the URL argument must be present, otherwise it must be omitted.

100 Continue

ErrorDocument Continue | Sample 100 Continue
This means that the server has received the request headers, and that the client should proceed to send the request body (in case of a request which needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the requests headers alone, a client must send Expect: 100-continue as a header in its initial request (see RFC 2616 14.20 Expect header) and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).

101 Switching Protocols

ErrorDocument Switching Protocols | Sample 101 Switching Protocols
This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.[3]

102 Processing

ErrorDocument Processing | Sample 102 Processing
(WebDAV) — (RFC 2518 )

200 OK

ErrorDocument OK | Sample 200 OK
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.

201 Created

ErrorDocument Created | Sample 201 Created
The request has been fulfilled and resulted in a new resource being created.

202 Accepted

ErrorDocument Accepted | Sample 202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.

203 Non-Authoritative Information

ErrorDocument Non-Authoritative Information | Sample 203 Non-Authoritative Information
The server successfully processed the request, but is returning information that may be from another source.

204 No Content

ErrorDocument No Content | Sample 204 No Content
The server successfully processed the request, but is not returning any content.

205 Reset Content

ErrorDocument Reset Content | Sample 205 Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.

206 Partial Content

ErrorDocument Partial Content | Sample 206 Partial Content
The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.

207 Multi-Status

ErrorDocument Multi-Status | Sample 207 Multi-Status
(WebDAV) — The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

226 IM Used

ErrorDocument IM Used | Sample 226 IM Used
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. The actual current instance might not be available except by combining this response with other previous or future responses, as appropriate for the specific instance-manipulation(s).

300 Multiple Choices

ErrorDocument Multiple Choices | Sample 300 Multiple Choices
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.

301 Moved Permanently

ErrorDocument Moved Permanently | Sample 301 Moved Permanently
This and all future requests should be directed to the given URI.

302 Found

ErrorDocument Found | Sample 302 Found
This is the most popular redirect code[citation needed], but also an example of industrial practice contradicting the standard. HTTP/1.0 specification (RFC 1945 ) required the client to perform a temporary redirect (the original describing phrase was «Moved Temporarily»), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to disambiguate between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.

303 See Other

ErrorDocument See Other | Sample 303 See Other
The response to the request can be found under another URI using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.

304 Not Modified

ErrorDocument Not Modified | Sample 304 Not Modified
Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.

305 Use Proxy

ErrorDocument Use Proxy | Sample 305 Use Proxy
Many HTTP clients (such as Mozilla[4] and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.

306 Switch Proxy

ErrorDocument Switch Proxy | Sample 306 Switch Proxy
No longer used.

307 Temporary Redirect

ErrorDocument Temporary Redirect | Sample 307 Temporary Redirect
In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.

400 Bad Request

ErrorDocument Bad Request | Sample 400 Bad Request
The request contains bad syntax or cannot be fulfilled.

401 Unauthorized

ErrorDocument Unauthorized | Sample 401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.

402 Payment Required

ErrorDocument Payment Required | Sample 402 Payment Required
The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code has never been used.

403 Forbidden

ErrorDocument Forbidden | Sample 403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

404 Not Found

ErrorDocument Not Found | Sample 404 Not Found
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.

405 Method Not Allowed

ErrorDocument Method Not Allowed | Sample 405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.

406 Not Acceptable

ErrorDocument Not Acceptable | Sample 406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.

407 Proxy Authentication Required

ErrorDocument Proxy Authentication Required | Sample 407 Proxy Authentication Required
Required

408 Request Timeout

ErrorDocument Request Timeout | Sample 408 Request Timeout
The server timed out waiting for the request.

409 Conflict

ErrorDocument Conflict | Sample 409 Conflict
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.

410 Gone

ErrorDocument Gone | Sample 410 Gone
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed; however, it is not necessary to return this code and a 404 Not Found can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.

411 Length Required

ErrorDocument Length Required | Sample 411 Length Required
The request did not specify the length of its content, which is required by the requested resource.

412 Precondition Failed

ErrorDocument Precondition Failed | Sample 412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.

413 Request Entity Too Large

ErrorDocument Request Entity Too Large | Sample 413 Request Entity Too Large
The request is larger than the server is willing or able to process.

414 Request-URI Too Long

ErrorDocument Request-URI Too Long | Sample 414 Request-URI Too Long
The URI provided was too long for the server to process.

415 Unsupported Media Type

ErrorDocument Unsupported Media Type | Sample 415 Unsupported Media Type
The request did not specify any media types that the server or resource supports. For example the client specified that an image resource should be served as image/svg+xml, but the server cannot find a matching version of the image.

416 Requested Range Not Satisfiable

ErrorDocument Requested Range Not Satisfiable | Sample 416 Requested Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion (for example, if the client asked for a part of the file that lies beyond the end of the file).

417 Expectation Failed

ErrorDocument Expectation Failed | Sample 417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.

418 I’m a teapot

ErrorDocument I’m a teapot | Sample 418 I’m a teapot
The HTCPCP server is a teapot. The responding entity MAY be short and stout. Defined by the April Fools specification RFC 2324. See Hyper Text Coffee Pot Control Protocol for more information.

422 Unprocessable Entity

ErrorDocument Unprocessable Entity | Sample 422 Unprocessable Entity
(WebDAV) (RFC 4918 ) — The request was well-formed but was unable to be followed due to semantic errors.

423 Locked

ErrorDocument Locked | Sample 423 Locked
(WebDAV) (RFC 4918 ) — The resource that is being accessed is locked

424 Failed Dependency

ErrorDocument Failed Dependency | Sample 424 Failed Dependency
(WebDAV) (RFC 4918 ) — The request failed due to failure of a previous request (e.g. a PROPPATCH).

425 Unordered Collection

ErrorDocument Unordered Collection | Sample 425 Unordered Collection
Defined in drafts of WebDav Advanced Collections, but not present in «Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol» (RFC 3648).

426 Upgrade Required

ErrorDocument Upgrade Required | Sample 426 Upgrade Required
(RFC 2817 ) — The client should switch to TLS/1.0.

449 Retry With

ErrorDocument Retry With | Sample 449 Retry With
A Microsoft extension. The request should be retried after doing the appropriate action.

500 Internal Server Error

ErrorDocument Internal Server Error | Sample 500 Internal Server Error
A generic error message, given when no more specific message is suitable.

501 Not Implemented

ErrorDocument Not Implemented | Sample 501 Not Implemented
The server either does not recognise the request method, or it lacks the ability to fulfil the request.

502 Bad Gateway

ErrorDocument Bad Gateway | Sample 502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503 Service Unavailable

ErrorDocument Service Unavailable | Sample 503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

504 Gateway Timeout

ErrorDocument Gateway Timeout | Sample 504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely request from the upstream server.

505 HTTP Version Not Supported

ErrorDocument HTTP Version Not Supported | Sample 505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.

506 Variant Also Negotiates

ErrorDocument Variant Also Negotiates | Sample 506 Variant Also Negotiates
(RFC 2295 ) — Transparent content negotiation for the request, results in a circular reference.

507 Insufficient Storage

ErrorDocument Insufficient Storage | Sample 507 Insufficient Storage
(WebDAV) (RFC 4918 )

509 Bandwidth Limit Exceeded

ErrorDocument Bandwidth Limit Exceeded | Sample 509 Bandwidth Limit Exceeded
(Apache bw/limited extension) — This status code, while used by many servers, is not specified in any RFCs.

510 Not Extended

ErrorDocument Not Extended | Sample 510 Not Extended
(RFC 2774 ) — Further extensions to the request are required for the server to fulfil it.

1xx Info / Informational

HTTP_INFO — Request received, continuing process. Indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line.

• 100 Continue — HTTP_CONTINUE
• 101 Switching Protocols — HTTP_SWITCHING_PROTOCOLS
• 102 Processing — HTTP_PROCESSING

2xx Success / OK

HTTP_SUCCESS — The action was successfully received, understood, and accepted. Indicates that the client’s request was successfully received, understood, and accepted.

• 200 OK — HTTP_OK
• 201 Created — HTTP_CREATED
• 202 Accepted — HTTP_ACCEPTED
• 203 Non-Authoritative Information — HTTP_NON_AUTHORITATIVE
• 204 No Content — HTTP_NO_CONTENT
• 205 Reset Content — HTTP_RESET_CONTENT
• 206 Partial Content — HTTP_PARTIAL_CONTENT
• 207 Multi-Status — HTTP_MULTI_STATUS

3xx Redirect

HTTP_REDIRECT — The client must take additional action to complete the request. Indicates that further action needs to be taken by the user-agent in order to fulfill the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent should not automatically redirect a request more than 5 times, since such redirections usually indicate an infinite loop.

• 300 Multiple Choices — HTTP_MULTIPLE_CHOICES
• 301 Moved Permanently — HTTP_MOVED_PERMANENTLY
• 302 Found — HTTP_MOVED_TEMPORARILY
• 303 See Other — HTTP_SEE_OTHER
• 304 Not Modified — HTTP_NOT_MODIFIED
• 305 Use Proxy — HTTP_USE_PROXY
• 306 unused — UNUSED
• 307 Temporary Redirect — HTTP_TEMPORARY_REDIRECT

4xx Client Error

HTTP_CLIENT_ERROR — The request contains bad syntax or cannot be fulfilled. Indicates case where client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.

• 400 Bad Request — HTTP_BAD_REQUEST
• 401 Authorization Required — HTTP_UNAUTHORIZED
• 402 Payment Required — HTTP_PAYMENT_REQUIRED
• 403 Forbidden — HTTP_FORBIDDEN
• 404 Not Found — HTTP_NOT_FOUND
• 405 Method Not Allowed — HTTP_METHOD_NOT_ALLOWED
• 406 Not Acceptable — HTTP_NOT_ACCEPTABLE
• 407 Proxy Authentication Required — HTTP_PROXY_AUTHENTICATION_REQUIRED
• 408 Request Time-out — HTTP_REQUEST_TIME_OUT
• 409 Conflict — HTTP_CONFLICT
• 410 Gone — HTTP_GONE
• 411 Length Required — HTTP_LENGTH_REQUIRED
• 412 Precondition Failed — HTTP_PRECONDITION_FAILED
• 413 Request Entity Too Large — HTTP_REQUEST_ENTITY_TOO_LARGE
• 414 Request-URI Too Large — HTTP_REQUEST_URI_TOO_LARGE
• 415 Unsupported Media Type — HTTP_UNSUPPORTED_MEDIA_TYPE
• 416 Requested Range Not Satisfiable — HTTP_RANGE_NOT_SATISFIABLE
• 417 Expectation Failed — HTTP_EXPECTATION_FAILED
• 418 I’m a teapot — UNUSED
• 419 unused — UNUSED
• 420 unused — UNUSED
• 421 unused — UNUSED
• 422 Unprocessable Entity — HTTP_UNPROCESSABLE_ENTITY
• 423 Locked — HTTP_LOCKED
• 424 Failed Dependency — HTTP_FAILED_DEPENDENCY
• 425 No code — HTTP_NO_CODE
• 426 Upgrade Required — HTTP_UPGRADE_REQUIRED

5xx Server Error

HTTP_SERVER_ERROR — The server failed to fulfill an apparently valid request. Indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents should display any included entity to the user. These response codes are applicable to any request method.

• 500 Internal Server Error — HTTP_INTERNAL_SERVER_ERROR
• 501 Method Not Implemented — HTTP_NOT_IMPLEMENTED
• 502 Bad Gateway — HTTP_BAD_GATEWAY
• 503 Service Temporarily Unavailable — HTTP_SERVICE_UNAVAILABLE
• 504 Gateway Time-out — HTTP_GATEWAY_TIME_OUT
• 505 HTTP Version Not Supported — HTTP_VERSION_NOT_SUPPORTED
• 506 Variant Also Negotiates — HTTP_VARIANT_ALSO_VARIES
• 507 Insufficient Storage — HTTP_INSUFFICIENT_STORAGE
• 508 unused — UNUSED
• 509 unused — UNUSED
• 510 Not Extended — HTTP_NOT_EXTENDED

Quick Start to triggering ErrorDocuments for each Status Code

Let start with a quick and easy example. Add the following Redirect rules to your htaccess file, then open your browser and goto each url like yoursite.com/e/400. Don’t create an /e/ directory or any files.

Redirect 400 /e/400
Redirect 503 /e/503
Redirect 405 /e/405

Automate the ErrorDocument Triggering

The htaccess Redirects

When a Status code is encountered, Apache outputs the Header and the ErrorDocument for that error code. So you can view any Header and the default ErrorDocument, by causing that numerical error code, which is caused by the Status Code.

For instance, if you request a file that doesn’t exist, a 404 Not Found Header is issued and the corresponding ErrorDocument is served with the 404 Not Found Header.

Redirect 100 /e/100
Redirect 101 /e/101
Redirect 102 /e/102
Redirect 200 /e/200
Redirect 201 /e/201
Redirect 202 /e/202
Redirect 203 /e/203
Redirect 204 /e/204
Redirect 205 /e/205
Redirect 206 /e/206
Redirect 207 /e/207
Redirect 300 /e/300 https://www.askapache.com/?s=300
Redirect 301 /e/301 https://www.askapache.com/?s=301
Redirect 302 /e/302 https://www.askapache.com/?s=302
Redirect 303 /e/303 https://www.askapache.com/?s=303
Redirect 304 /e/304 https://www.askapache.com/?s=304
Redirect 305 /e/305 https://www.askapache.com/?s=305
Redirect 306 /e/306 https://www.askapache.com/?s=306
Redirect 307 /e/307 https://www.askapache.com/?s=307
Redirect 400 /e/400
Redirect 401 /e/401
Redirect 402 /e/402
Redirect 403 /e/403
Redirect 404 /e/404
Redirect 405 /e/405
Redirect 406 /e/406
Redirect 407 /e/407
Redirect 408 /e/408
Redirect 409 /e/409
Redirect 410 /e/410
Redirect 411 /e/411
Redirect 412 /e/412
Redirect 413 /e/413
Redirect 414 /e/414
Redirect 415 /e/415
Redirect 416 /e/416
Redirect 417 /e/417
Redirect 418 /e/418
Redirect 419 /e/419
Redirect 420 /e/420
Redirect 421 /e/421
Redirect 422 /e/422
Redirect 423 /e/423
Redirect 424 /e/424
Redirect 425 /e/425
Redirect 426 /e/426
Redirect 500 /e/500
Redirect 501 /e/501
Redirect 502 /e/502
Redirect 503 /e/503
Redirect 504 /e/504
Redirect 505 /e/505
Redirect 506 /e/506
Redirect 507 /e/507
Redirect 508 /e/508
Redirect 509 /e/509
Redirect 510 /e/510

PHP script that gets and outputs the Headers/Content

Now all I have to do is add 57 Redirect Directives to my htaccess, and then request each of them 1 at a time from my browser to see the result, and use a packet sniffing program like WireShark to see the Headers. Uh, scratch that, that would take way too long!

Instead I hacked up a simple php script using cURL to automate sending GET Requests to each of the 57 Redirect URL-paths. A side benefit of using the php script is that it performs all 57 Requests concurrently and saves each Requests returned headers and content to an output buffer. After all 57 have been queried, the output buffer is flushed to the browser.

<?php
$SITENAME='https://www.askapache.com';

$CODES = array(array('100','101','102'),
array('200','201','202','203','204','205','206','207'),
array('300','301','302','303','304','305','306','307'),
array('400','401','402','403','404','405','406','407','408','409','410','411','412','413',
'414','415','416','417','418','419','420','421','422','423','424','425','426'),
array('500','501','502','503','504','505','506','507','508','509','510'));

$TMPSAVETO='/tmp/'.time().'.txt';

# if file exists then delete it
if(is_file($TMPSAVETO))unlink($TMPSAVETO);

foreach($CODES as $keyd => $res)
{
foreach($res as $key)
{
$ch = curl_init("$SITENAME/e/$key");
$fp = fopen ($TMPSAVETO, "a");
curl_setopt ($ch, CURLOPT_FILE, $fp);
curl_setopt ($ch, CURLOPT_FOLLOWLOCATION ,1);
curl_setopt ($ch, CURLOPT_HEADER ,1);
curl_exec ($ch);
curl_close ($ch);
fclose ($fp);
}
}
$OUT='';
ob_start();
header ("Content-Type: text/plain;");
readfile($TMPSAVETO);
$OUT=ob_get_clean();
echo $OUT;
unlink($TMPSAVETO);
exit;
?>

Headers and Content Returned

100 Continue

HTTP/1.1 100 Continue
<html>
<head>
<title>100 Continue</title>
</head>
<body>
<h1 id="Continue">Continue <a class="sl" href="#Continue"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

101 Switching Protocols

HTTP/1.1 101 Switching Protocols<html>
<head>
<title>101 Switching Protocols</title>
</head>
<body>
<h1 id="Switching_Protocols">Switching Protocols <a class="sl" href="#Switching_Protocols"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

102 Processing

HTTP/1.1 102 Processing
X-Pad: avoid browser bug<html>
<head>
<title>102 Processing</title>
</head>
<body>
<h1 id="Processing">Processing <a class="sl" href="#Processing"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

200 OK

HTTP/1.1 200 OK
<html>
<head>
<title>200 OK</title>
</head>
<body>
<h1 id="OK">OK <a class="sl" href="#OK"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

201 Created

HTTP/1.1 201 Created
<html>
<head>
<title>201 Created</title>
</head>
<body>
<h1 id="Created">Created <a class="sl" href="#Created"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

202 Accepted

HTTP/1.1 202 Accepted
<html>
<head>
<title>202 Accepted</title>
</head>
<body>
<h1 id="Accepted">Accepted <a class="sl" href="#Accepted"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

HTTP/1.1 203 Non-Authoritative Information
<html>
<head>
<title>203 Non-Authoritative Information</title>
</head>
<body>
<h1 id="Non-Authoritative_Information">Non-Authoritative Information <a class="sl" href="#Non-Authoritative_Information"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

204 No Content

HTTP/1.1 204 No Content
Content-Type: text/plain; charset=UTF-8

205 Reset Content

HTTP/1.1 205 Reset Content<html>
<head>
<title>205 Reset Content</title>
</head>
<body>
<h1 id="Reset_Content">Reset Content <a class="sl" href="#Reset_Content"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

206 Partial Content

HTTP/1.1 206 Partial Content<html>
<head>
<title>206 Partial Content</title>
</head>
<body>
<h1 id="Partial_Content">Partial Content <a class="sl" href="#Partial_Content"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

207 Multi-Status

HTTP/1.1 207 Multi-Status
X-Pad: avoid browser bug<html>
<head>
<title>207 Multi-Status</title>
</head>
<body>
<h1 id="Multi-Status">Multi-Status <a class="sl" href="#Multi-Status"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

300 Multiple Choices

HTTP/1.1 300 Multiple Choices
Location: https://www.askapache.com/?s=300<html>
<head>
<title>300 Multiple Choices</title>
</head>
<body>
<h1 id="Multiple_Choices">Multiple Choices <a class="sl" href="#Multiple_Choices"></a></h1>
</body>
</html>

301 Moved Permanently

HTTP/1.1 301 Moved Permanently
Location: https://www.askapache.com/?s=301<html>
<head>
<title>301 Moved Permanently</title>
</head>
<body>
<h1 id="Moved_Permanently">Moved Permanently <a class="sl" href="#Moved_Permanently"></a></h1>
<p>The document has moved  <a href="https://www.askapache.com/?s=301">here</a> .</p>
</body>
</html>

302 Found

HTTP/1.1 302 Found
Location: https://www.askapache.com/?s=302<html>
<head>
<title>302 Found</title>
</head>
<body>
<h1 id="Found">Found <a class="sl" href="#Found"></a></h1>
<p>The document has moved  <a href="https://www.askapache.com/?s=302">here</a> .</p>
</body>
</html>

303 See Other

HTTP/1.1 303 See Other
Location: https://www.askapache.com/?s=303<html>
<head>
<title>303 See Other</title>
</head>
<body>
<h1 id="See_Other">See Other <a class="sl" href="#See_Other"></a></h1>
<p>The answer to your request is located  <a href="https://www.askapache.com/?s=303">here</a> .</p>
</body>
</html>

304 Not Modified

HTTP/1.1 304 Not Modified

305 Use Proxy

HTTP/1.1 305 Use Proxy
Location: https://www.askapache.com/?s=305<html>
<head>
<title>305 Use Proxy</title>
</head>
<body>
<h1 id="Use_Proxy">Use Proxy <a class="sl" href="#Use_Proxy"></a></h1>
<p>This resource is only accessible through the proxy https://www.askapache.com/?s=305<br />You will need to configure your client to use that proxy.</p>
</body>
</html>

306 unused

HTTP/1.1 306 unused
Location: https://www.askapache.com/?s=306<html>
<head>
<title>306 unused</title>
</head>
<body>
<h1 id="unused">unused <a class="sl" href="#unused"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

307 Temporary Redirect

HTTP/1.1 307 Temporary Redirect
Location: https://www.askapache.com/?s=307<html>
<head>
<title>307 Temporary Redirect</title>
</head>
<body>
<h1 id="Temporary_Redirect">Temporary Redirect <a class="sl" href="#Temporary_Redirect"></a></h1>
<p>The document has moved  <a href="https://www.askapache.com/?s=307">here</a> .</p>
</body>
</html>

400 Bad Request

HTTP/1.1 400 Bad Request
Connection: close<html>
<head>
<title>400 Bad Request</title>
</head>
<body>
<h1 id="Bad_Request">Bad Request <a class="sl" href="#Bad_Request"></a></h1>
<p>Your browser sent a request that this server could not understand.</p>
</body>
</html>

401 Authorization Required

HTTP/1.1 401 Authorization Required<html>
<head>
<title>401 Authorization Required</title>
</head>
<body>
<h1 id="Authorization_Required">Authorization Required <a class="sl" href="#Authorization_Required"></a></h1>
<p>This server could not verify that you
    are authorized to access the document
    requested.  Either you supplied the wrong
    credentials (e.g., bad password), or your
    browser doesn't understand how to supply
    the credentials required.</p>
<p>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body>
</html>

402 Payment Required

HTTP/1.1 402 Payment Required<html>
<head>
<title>402 Payment Required</title>
</head>
<body>
<h1 id="Payment_Required">Payment Required <a class="sl" href="#Payment_Required"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

403 Forbidden

HTTP/1.1 403 Forbidden<html>
<head>
<title>403 Forbidden</title>
</head>
<body>
<h1 id="Forbidden">Forbidden <a class="sl" href="#Forbidden"></a></h1>
<p>You don't have permission to access /e/403 on this server.</p>
<p>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body>
</html>

404 Not Found

HTTP/1.1 404 Not Found<html>
<head>
<title>404 Not Found</title>
</head>
<body>
<h1 id="Not_Found">Not Found <a class="sl" href="#Not_Found"></a></h1>
<p>The requested URL /e/404 was not found on this server.</p>
</body>
</html>

NOTE:
You will most definately want to check out and use the Google 404 Error Page if you run WordPress.

405 Method Not Allowed

HTTP/1.1 405 Method Not Allowed
Allow: TRACE
<html>
<head>
<title>405 Method Not Allowed</title>
</head>
<body>
<h1 id="Method_Allowed">Method Not Allowed <a class="sl" href="#Method_Allowed"></a></h1>
<p>The requested method GET is not allowed for the URL /e/405.</p>
</body>
</html>

406 Not Acceptable

HTTP/1.1 406 Not Acceptable
<html>
<head>
<title>406 Not Acceptable</title>
</head>
<body>
<h1 id="Not_Acceptable">Not Acceptable <a class="sl" href="#Not_Acceptable"></a></h1>
<p>An appropriate representation of the requested resource /e/406 could not be found on this server.</p>
</body>
</html>

407 Proxy Authentication Required

HTTP/1.1 407 Proxy Authentication Required<html>
<head>
<title>407 Proxy Authentication Required</title>
</head>
<body>
<h1 id="Proxy_Authentication_Required">Proxy Authentication Required <a class="sl" href="#Proxy_Authentication_Required"></a></h1>
<p>This server could not verify that you
    are authorized to access the document
    requested.  Either you supplied the wrong
    credentials (e.g., bad password), or your
    browser doesn't understand how to supply
    the credentials required.</p>
</body>
</html>

408 Request Time-out

HTTP/1.1 408 Request Time-out
Connection: close
<html>
<head>
<title>408 Request Time-out</title>
</head>
<body>
<h1 id="Request_Time-out">Request Time-out <a class="sl" href="#Request_Time-out"></a></h1>
<p>Server timeout waiting for the HTTP request from the client.</p>
</body>
</html>

409 Conflict

HTTP/1.1 409 Conflict
<html>
<head>
<title>409 Conflict</title>
</head>
<body>
<h1 id="Conflict">Conflict <a class="sl" href="#Conflict"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

410 Gone

HTTP/1.1 410 Gone
<html>
<head>
<title>410 Gone</title>
</head>
<body>
<h1 id="Gone">Gone <a class="sl" href="#Gone"></a></h1>
<p>The requested resource<br />/e/410<br />is no longer available on this server and there is no forwarding address.
    Please remove all references to this resource.</p>
</body>
</html>

411 Length Required

HTTP/1.1 411 Length Required
Connection: close
<html>
<head>
<title>411 Length Required</title>
</head>
<body>
<h1 id="Length_Required">Length Required <a class="sl" href="#Length_Required"></a></h1>
<p>A request of the requested method GET requires a valid Content-length.</p>
</body>
</html>

412 Precondition Failed

HTTP/1.1 412 Precondition Failed
<html>
<head>
<title>412 Precondition Failed</title>
</head>
<body>
<h1 id="Precondition_Failed">Precondition Failed <a class="sl" href="#Precondition_Failed"></a></h1>
<p>The precondition on the request for the URL /e/412 evaluated to false.</p>
</body>
</html>

413 Request Entity Too Large

HTTP/1.1 413 Request Entity Too Large
Connection: close<html>
<head>
<title>413 Request Entity Too Large</title>
</head>
<body>
<h1 id="Request_Entity_Large">Request Entity Too Large <a class="sl" href="#Request_Entity_Large"></a></h1>
The requested resource<br />/e/413<br />does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.
</body>
</html>

414 Request-URI Too Large

HTTP/1.1 414 Request-URI Too Large
Connection: close<html>
<head>
<title>414 Request-URI Too Large</title>
</head>
<body>
<h1 id="Request-URI_Large">Request-URI Too Large <a class="sl" href="#Request-URI_Large"></a></h1>
<p>The requested URL's length exceeds the capacity limit for this server.</p>
</body>
</html>

415 Unsupported Media Type

HTTP/1.1 415 Unsupported Media Type<html>
<head>
<title>415 Unsupported Media Type</title>
</head>
<body>
<h1 id="Unsupported_Type">Unsupported Media Type <a class="sl" href="#Unsupported_Type"></a></h1>
<p>The supplied request data is not in a format acceptable for processing by this resource.</p>
</body>
</html>

416 Requested Range Not Satisfiable

HTTP/1.1 416 Requested Range Not Satisfiable

417 Expectation Failed

HTTP/1.1 417 Expectation Failed<html>
<head>
<title>417 Expectation Failed</title>
</head>
<body>
<h1 id="Expectation_Failed">Expectation Failed <a class="sl" href="#Expectation_Failed"></a></h1>
<p>The expectation given in the Expect request-header field could not be met by this server.</p>
<p>The client sent Expect: </p>
</body>
</html>

418 I’m a teapot

HTTP/1.1 418 I'm a teapot<html>
<head>
<title>418 I'm a teapot</title>
</head>
<body>
<h1 id="Im_teapot">I'm a teapot <a class="sl" href="#Im_teapot"></a></h1>
<p>Unfortunately this coffee machine is out of coffee.</p>
</body>
</html>

419 unused

HTTP/1.1 419 unused<html>
<head>
<title>419 unused</title>
</head>
<body>
<h1 id="unused-s0">unused <a class="sl" href="#unused-s0"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

420 unused

HTTP/1.1 420 unused<html>
<head>
<title>420 unused</title>
</head>
<body>
<h1 id="unused-s0-s1">unused <a class="sl" href="#unused-s0-s1"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

421 unused

HTTP/1.1 421 unused<html>
<head>
<title>421 unused</title>
</head>
<body>
<h1 id="unused-s0-s1-s2">unused <a class="sl" href="#unused-s0-s1-s2"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

422 Unprocessable Entity

HTTP/1.1 422 Unprocessable Entity<html>
<head>
<title>422 Unprocessable Entity</title>
</head>
<body>
<h1 id="Unprocessable_Entity">Unprocessable Entity <a class="sl" href="#Unprocessable_Entity"></a></h1>
<p>The server understands the media type of the
    request entity, but was unable to process the
    contained instructions.</p>
</body>
</html>

423 Locked

HTTP/1.1 423 Locked<html>
<head>
<title>423 Locked</title>
</head>
<body>
<h1 id="Locked">Locked <a class="sl" href="#Locked"></a></h1>
<p>The requested resource is currently locked.
    The lock must be released or proper identification
    given before the method can be applied.</p>
</body>
</html>

424 Failed Dependency

HTTP/1.1 424 Failed Dependency<html>
<head>
<title>424 Failed Dependency</title>
</head>
<body>
<h1 id="Failed_Dependency">Failed Dependency <a class="sl" href="#Failed_Dependency"></a></h1>
<p>The method could not be performed on the resource
    because the requested action depended on another
    action and that other action failed.</p>
</body>
</html>

425 No code

HTTP/1.1 425 No code<html>
<head>
<title>425 No code</title>
</head>
<body>
<h1 id="No_code">No code <a class="sl" href="#No_code"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

426 Upgrade Required

HTTP/1.1 426 Upgrade Required<html>
<head>
<title>426 Upgrade Required</title>
</head>
<body>
<h1 id="Upgrade_Required">Upgrade Required <a class="sl" href="#Upgrade_Required"></a></h1>
<p>The requested resource can only be retrieved
    using SSL.  The server is willing to upgrade the current
    connection to SSL, but your client doesn't support it.
    Either upgrade your client, or try requesting the page
    using https:// </p>
</body>
</html>

500 Internal Server Error

HTTP/1.1 500 Internal Server Error
Connection: close<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h1 id="Internal_Server_Error">Internal Server Error <a class="sl" href="#Internal_Server_Error"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
<p>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body>
</html>

501 Method Not Implemented

HTTP/1.1 501 Method Not Implemented
Allow: TRACE
Connection: close<html>
<head>
<title>501 Method Not Implemented</title>
</head>
<body>
<h1 id="Method_Implemented">Method Not Implemented <a class="sl" href="#Method_Implemented"></a></h1>
<p>GET to /e/501 not supported.</p>
</body>
</html>

502 Bad Gateway

HTTP/1.1 502 Bad Gateway
X-Pad: avoid browser bug<html>
<head>
<title>502 Bad Gateway</title>
</head>
<body>
<h1 id="Bad_Gateway">Bad Gateway <a class="sl" href="#Bad_Gateway"></a></h1>
<p>The proxy server received an invalid
    response from an upstream server.</p>
</body>
</html>

503 Service Temporarily Unavailable

HTTP/1.1 503 Service Temporarily Unavailable
Connection: close<html>
<head>
<title>503 Service Temporarily Unavailable</title>
</head>
<body>
<h1 id="Service_Temporarily_Unavailable">Service Temporarily Unavailable <a class="sl" href="#Service_Temporarily_Unavailable"></a></h1>
<p>The server is temporarily unable to service your
    request due to maintenance downtime or capacity
    problems. Please try again later.</p>
</body>
</html>

504 Gateway Time-out

HTTP/1.1 504 Gateway Time-out<html>
<head>
<title>504 Gateway Time-out</title>
</head>
<body>
<h1 id="Gateway_Time-out">Gateway Time-out <a class="sl" href="#Gateway_Time-out"></a></h1>
<p>The proxy server did not receive a timely response
    from the upstream server.</p>
</body>
</html>

505 HTTP Version Not Supported

HTTP/1.1 505 HTTP Version Not Supported<html>
<head>
<title>505 HTTP Version Not Supported</title>
</head>
<body>
<h1 id="HTTP_Supported">HTTP Version Not Supported <a class="sl" href="#HTTP_Supported"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

506 Variant Also Negotiates

HTTP/1.1 506 Variant Also Negotiates<html>
<head>
<title>506 Variant Also Negotiates</title>
</head>
<body>
<h1 id="Variant_Negotiates">Variant Also Negotiates <a class="sl" href="#Variant_Negotiates"></a></h1>
<p>A variant for the requested resource
    <pre>
    /e/506
    </pre>
    is itself a negotiable resource. This indicates a configuration error.</p>
</body>
</html>

507 Insufficient Storage

HTTP/1.1 507 Insufficient Storage<html>
<head>
<title>507 Insufficient Storage</title>
</head>
<body>
<h1 id="Insufficient_Storage">Insufficient Storage <a class="sl" href="#Insufficient_Storage"></a></h1>
<p>The method could not be performed on the resource
    because the server is unable to store the
    representation needed to successfully complete the
    request.  There is insufficient free space left in
    your storage allocation.</p>
</body>
</html>

508 unused

HTTP/1.1 508 unused<html>
<head>
<title>508 unused</title>
</head>
<body>
<h1 id="unused-s0-s1-s2">unused <a class="sl" href="#unused-s0-s1-s2"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

509 unused

HTTP/1.1 509 unused
<html>
<head>
<title>509 unused</title>
</head>
<body>
<h1 id="unused-s0-s1-s2">unused <a class="sl" href="#unused-s0-s1-s2"></a></h1>
<p>The server encountered an internal error or misconfigurationand was unable to complete your request.</p>
<p>Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
</body>
</html>

510 Not Extended

HTTP/1.1 510 Not Extended
X-Pad: avoid browser bug
<html>
<head>
<title>510 Not Extended</title>
</head>
<body>
<h1 id="Not_Extended">Not Extended <a class="sl" href="#Not_Extended"></a></h1>
<p>A mandatory extension policy in the request is not
    accepted by the server for this resource.</p>
</body>
</html>

Apache Source Code

httpd.h

From httpd.h

/**
* The size of the static array in http_protocol.c for storing
* all of the potential response status-lines (a sparse table).
* A future version should dynamically generate the apr_table_t at startup.
*/
#define RESPONSE_CODES 57
#define HTTP_CONTINUE            100
#define HTTP_SWITCHING_PROTOCOLS       101
#define HTTP_PROCESSING          102
#define HTTP_OK              200
#define HTTP_CREATED             201
#define HTTP_ACCEPTED            202
#define HTTP_NON_AUTHORITATIVE       203
#define HTTP_NO_CONTENT          204
#define HTTP_RESET_CONTENT         205
#define HTTP_PARTIAL_CONTENT         206
#define HTTP_MULTI_STATUS          207
#define HTTP_MULTIPLE_CHOICES        300
#define HTTP_MOVED_PERMANENTLY       301

#define HTTP_MOVED_TEMPORARILY       302
#define HTTP_SEE_OTHER           303
#define HTTP_NOT_MODIFIED          304
#define HTTP_USE_PROXY           305
#define HTTP_TEMPORARY_REDIRECT      307
#define HTTP_BAD_REQUEST           400
#define HTTP_UNAUTHORIZED          401
#define HTTP_PAYMENT_REQUIRED        402
#define HTTP_FORBIDDEN           403
#define HTTP_NOT_FOUND           404
#define HTTP_METHOD_NOT_ALLOWED      405
#define HTTP_NOT_ACCEPTABLE        406
#define HTTP_PROXY_AUTHENTICATION_REQUIRED 407
#define HTTP_REQUEST_TIME_OUT        408
#define HTTP_CONFLICT            409
#define HTTP_GONE              410
#define HTTP_LENGTH_REQUIRED         411
#define HTTP_PRECONDITION_FAILED       412
#define HTTP_REQUEST_ENTITY_TOO_LARGE    413
#define HTTP_REQUEST_URI_TOO_LARGE     414
#define HTTP_UNSUPPORTED_MEDIA_TYPE    415
#define HTTP_RANGE_NOT_SATISFIABLE     416
#define HTTP_EXPECTATION_FAILED      417
#define HTTP_UNPROCESSABLE_ENTITY      422
#define HTTP_LOCKED            423
#define HTTP_FAILED_DEPENDENCY       424
#define HTTP_UPGRADE_REQUIRED        426
#define HTTP_INTERNAL_SERVER_ERROR     500
#define HTTP_NOT_IMPLEMENTED         501
#define HTTP_BAD_GATEWAY           502
#define HTTP_SERVICE_UNAVAILABLE       503
#define HTTP_GATEWAY_TIME_OUT        504
#define HTTP_VERSION_NOT_SUPPORTED     505
#define HTTP_VARIANT_ALSO_VARIES       506
#define HTTP_INSUFFICIENT_STORAGE      507
#define HTTP_NOT_EXTENDED          510

/** is the status code informational */
#define ap_is_HTTP_INFO(x)     (((x) >= 100)&&((x) < 200))
/** is the status code OK ?*/
#define ap_is_HTTP_SUCCESS(x)    (((x) >= 200)&&((x) < 300))
/** is the status code a redirect */
#define ap_is_HTTP_REDIRECT(x)   (((x) >= 300)&&((x) < 400))
/** is the status code a error (client or server) */
#define ap_is_HTTP_ERROR(x)    (((x) >= 400)&&((x) < 600))
/** is the status code a client error  */
#define ap_is_HTTP_CLIENT_ERROR(x) (((x) >= 400)&&((x) < 500))
/** is the status code a server error  */
#define ap_is_HTTP_SERVER_ERROR(x) (((x) >= 500)&&((x) < 600))
/** is the status code a (potentially) valid response code?  */
#define ap_is_HTTP_VALID_RESPONSE(x) (((x) >= 100)&&((x) < 600))

/** should the status code drop the connection */
#define ap_status_drops_connection(x) 
(((x) == HTTP_BAD_REQUEST)       || 
((x) == HTTP_REQUEST_TIME_OUT)    || 
((x) == HTTP_LENGTH_REQUIRED)     || 
((x) == HTTP_REQUEST_ENTITY_TOO_LARGE) || 
((x) == HTTP_REQUEST_URI_TOO_LARGE) || 
((x) == HTTP_INTERNAL_SERVER_ERROR) || 
((x) == HTTP_SERVICE_UNAVAILABLE) || 
((x) == HTTP_NOT_IMPLEMENTED))

HTTP_INFO

Is the status code (x) informational?

x >= 100 && x < 200

HTTP_SUCCESS

Is the status code (x) OK?

x >= 200 && x < 300

HTTP_REDIRECT

Is the status code (x) a redirect?

x >= 300 && x < 400

HTTP_ERROR

Is the status code (x) a error (client or server)?

x >= 400 && x < 600

HTTP_CLIENT_ERROR

Is the status code (x) a client error?

x >= 400 && x < 500

HTTP_SERVER_ERROR

Is the status code (x) a server error?

x >= 500 && x < 600

HTTP_VALID_RESPONSE

Is the status code (x) a (potentially) valid response code?

x >= 100 && x < 600

http_protocol.c

From http_protocol.c

static const char * status_lines[RESPONSE_CODES] =
static const char * const status_lines[RESPONSE_CODES] =
"100 Continue",
"101 Switching Protocols",
"102 Processing",
"200 OK",
"201 Created",
"202 Accepted",
"203 Non-Authoritative Information",
"204 No Content",
"205 Reset Content",
"206 Partial Content",
"207 Multi-Status",
"300 Multiple Choices",
"301 Moved Permanently",
"302 Found",
"303 See Other",
"304 Not Modified",
"305 Use Proxy",
"306 unused",
"307 Temporary Redirect",
"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 Time-out",
"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 Requested Range Not Satisfiable",
"417 Expectation Failed",
"418 unused",
"419 unused",
"420 unused",
"421 unused",
"422 Unprocessable Entity",
"423 Locked",
"424 Failed Dependency",
"425 No code",
"426 Upgrade Required",
"500 Internal Server Error",
"501 Method Not Implemented",
"502 Bad Gateway",
"503 Service Temporarily Unavailable",
"504 Gateway Time-out",
"505 HTTP Version Not Supported",
"506 Variant Also Negotiates",
"507 Insufficient Storage",
"508 unused",
"509 unused",
"510 Not Extended"

IANA HTTP Status Code Registry

WordPress 2.8 Changes

I just learned that my modification to the WordPress core was accepted and will be implemented for version 2.8! This may mean WordPress is the only 100% HTTP/1.1 compliant software on the net! Below is the new list (I thought someone out there could use the php array) and as you can see, unfortunately418 I’m a teapotdidn’t make it

$wp_header_to_desc = array(
  100 => 'Continue',
  101 => 'Switching Protocols',
  102 => 'Processing',

  200 => 'OK',
  201 => 'Created',
  202 => 'Accepted',
  203 => 'Non-Authoritative Information',
  204 => 'No Content',
  205 => 'Reset Content',
  206 => 'Partial Content',
  207 => 'Multi-Status',
  226 => 'IM Used',

  300 => 'Multiple Choices',
  301 => 'Moved Permanently',
  302 => 'Found',
  303 => 'See Other',
  304 => 'Not Modified',
  305 => 'Use Proxy',
  306 => 'Reserved',
  307 => 'Temporary Redirect',

  400 => 'Bad Request',
  401 => 'Unauthorized',
  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 Long',
  415 => 'Unsupported Media Type',
  416 => 'Requested Range Not Satisfiable',
  417 => 'Expectation Failed',
  422 => 'Unprocessable Entity',
  423 => 'Locked',
  424 => 'Failed Dependency',
  426 => 'Upgrade Required',

  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'
);

RIPE WHOIS

All the status codes are standard HTTP codes ( http://www.iana.org/assignments/http-status-codes ).

Clients should avoid any form of coupling with the the text/plain error message contained in response body since it may change between different releases of the API and is only intended as a starting point for indentifying the real causes of the exception event.

The following table gives a brief description of the mapping between standard Whois V.3 responses and the related REST services status codes. Consider this table as just an example of the error mapping strategy, it may change with future releases.

Clients will have to define error messages generic enough to represent the four main error conditions, that are Bad Request, Forbidden, Not Found and Internal Server Error.

For example a possible mapping for client side error messages may be:

HTTP Status Code Links

1. zend HTTP
2. IANA registry
3. Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
4. Adobe Flash status code definitions (ie 408)
5. Microsoft Internet Information Server Status Codes and Sub-Codes
6. httplint
7. HTTP Headers, brief intro.
8. Common User-Agent Issues
9. [RFC2295] Transparent Content Negotiation in HTTP, March 1998.
10. [RFC2518] HTTP Extensions for Distributed Authoring — WEBDAV, February 1999.
11. [RFC2616] Hypertext Transfer Protocol — HTTP/1.1, June 1999.
12. [RFC2774] An HTTP Extension Framework, February 2000.
13. [RFC2817] Upgrading to TLS Within HTTP/1.1, May 2000.
14. [RFC3229] Delta encoding in HTTP, January 2002.
15. [RFC4918] HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV), June 2007.

Here is a list of most of the used http status codes with an explanation of what they mean.

Example usage: http client checks if chunked transfer encoding is allowed before sending the full request body. | |

Example usage: http client wants to switch from HTTP/1.1 to TLS/1.0 in order to set up a secure communication channel. | |

Example usage: a POST request to a remote script that generates a file on the server returns the status code 201 once the file has been succesfully created. | |

Example usage: Redirect permanent /foo http://www.example.com/bar or RewriteRule /foo http://www.example.com/bar [R=301]| |

Example usage: Redirect /foo http://www.example.com/bar or RewriteRule /foo http://www.example.com/bar [R]| |

Example usage: Redirect seeother /foo http://www.example.com/bar or RewriteRule /foo http://www.example.com/bar [R=303]| |

Example usage: Redirect 307 /foo http://www.example.com/bar or RewriteRule /foo http://www.example.com/bar [R=307] | RFC2616 Section 10 |

* No index file and indexing is turned off
* Deny rule matching the request
* Resource cannot be modified (the default response to a PUT request)
* Filesystem permission problems ([|Logs)

Always check the errorlog for what exactly went wrong.] |

Example usage: Redirect gone /foo http://www.example.com/bar | |

Example usage: a request body contains syntactically correct XML but semantically erroneous XML instructions. |RFC 2518 Section 10 |

Example usage: Alice is working on file foo.txt in a svn repository and locks the file at the end of her shift. In the mean time Bob was also working on foo.txt and tries to commit his changes trough a WebDAV-enabled httpd, which results in a response code 423. |RFC 2518 Section 10 |

Example usage: a PROPPATCH method is invoked with multiple changes to a resource, and one of these modifications fails. Since this method executes as a single atomic act, all changes must be able to be processed for the request to be succesfully completed. The other changes depended on the single failed modification, and the httpd returns status code 424. |RFC 2518 Section 10 |

Common causes are:
* Erroneous CGI / PHP (Bad filesystem permissions, scripting errors, malformed or missing shebang line, bad line endings, script timeouts, etc)
* Malformed directives in a .htaccess file
* Hardware / OS problems

Check out the link to detailed errors for more detailed errormessages. |Detailed errors |

Example usage: _ TODO: Documentation says this RFC is supported, but what config or type-map contents would result in this status code?_ |RFC 2295 Section 8 |

To get more details on the complete meaning of these codes you should consult the relevant standards, or more specifically RFC 2616 Section 10.

HTTP status codes can be found in the Apache HTTPD logfiles, this example shows a request that results in a ‘200’ response code:

  127.0.0.1 - foo [21/Jul/2011:13:37:42 +0100] "GET /bar HTTP/1.1" 200 23674 

Remember that, in the case of an error status code (4xx or 5xx), there will almost always be more details available in the Apache error log. See DistrosDefaultLayout if you don’t know where that file is kept.

Чем старее Рунет, тем чаще возникают потребности в знаниях кодов ошибок. Это связано с тем, что первые сайты в Рунете стареют и обросли большим количеством информации, которая в свою очередь могла переместиться на новый адрес или вообще быть удалена. В таком случае знания кодов ошибок и как их прописать на Веб сервере Apache необходимы всем Веб мастерам, дабы сохранить посетителя сайта и перенаправить его на нужную страничку. Об этом и будет сегодняшний пост.

Диапазон кодов           Значение ответа
  100-199                                    Информационный
  200-299                                    Запрос броузера успешен
  300-399                                    Запрос броузера переадресован, необходимы дальнейшие действия
  400-499                                    Запрос броузера является неполным
  500-599                                    Ошибки сервера

Ответы в диапазоне кодов 100-199 являются информационными. Они указывают, что запрос броузера принят и обрабатывается.

• 100 Continue — начальная часть запроса принята, и броузер может продолжать передачу запроса.
• 101 Switching Protocols — сервер выполняет требование броузера и переключает протоколы в соответствии с указанием, данным в поле заголовка Upgrade.

Ответы в диапазоне 200-299 означают, что запрос броузера обработан успешно.

• 200 ОК — запрос броузера обработан успешно и ответ сервера содержит затребованные данные.
• 201 Created — этот код состояния используется в случае создания нового URL.
• Вместе с этим кодом результата сервер выдает заголовок, который содержит информацию о том, куда были помещены новые данные.
• 202 Accepted — запрос принят, но обрабатывается не сразу. В теле содержимого ответа сервера может быть дана дополнительная информация о данном сеансе. Гарантии того, что сервер в конечном итоге удовлетворит запрос, нет — даже несмотря на то, что на момент приема запрос выглядел допустимым.
• 203 Non-Authoritative Information — информация в заголовке содержимого взята из локальной копии или у третьей стороны, а не с исходного сервера.
• 204 No Content — ответ содержит код состояния и заголовок, но тело содержимого отсутствует. При получении этого ответа броузер не должен обновлять свой документ. Обработчик чувствительных областей изображений может возвращать этот код, когда пользователь щелкает на бесполезных или пустых участках изображения.
• 205 Reset Content — броузер должен очистить используемую в данной транзакции форму для помещения дополнительных входных данных. Полезен для CGI-приложений, требующих ввода данных.
• 206 Partial Content — сервер возвращает лишь часть данных из общего затребованного объема.

Код ответа в диапазоне 300-399 означает, что запрос не выполнен и клиенту нужно предпринять некоторые дополнительные действия для удовлетворения запроса.

• 300 Multiple Choices — затребованный URL указывает на несколько ресурсов. Например, URL может обозначать документ, переведенный на несколько языков. В теле содержимого, возвращенном сервером, может находиться перечень более конкретных данных о том, как выбрать этот ресурс правильно.
• 301 Moved Permanently — затребованный URL уже не используется сервером и указанная в запросе операция не выполнена.
• 302 Moved Temporarily — в данный момент затребованный URL перемешен, но лишь временно.
• 303 See Other — затребованный URL можно найти по другому URL. Его следует выбрать методом GET по данному ресурсу.
• 304 Not Modified — тело содержимого не посылается и броузер должен использовать свою локальную копию.
• 305 Use Proxy — доступ к затребованному URL должен осуществляться через прокси-сервер.

Коды ответов в диапазоне 400-499 означают, что запрос броузера неполный. Эти коды могут также означать, что от броузера требуется дополнительная информация.

• 400 Bad Request — сервер обнаружил в запросе броузера синтаксическую ошибку.
• 401 Unauthorized — этот код результата показывает, что пославший запрос пользователь не имеет необходимых полномочий, и что при повторении запроса с указанием данного URL пользователь должен такие полномочия предоставить.
• 402 Payment Required — этот код в HTTP еще не реализован.
• 403 Forbidden — запрос отклонен по той причине, что сервер не хочет (или не имеет возможности) ответить броузеру.
• 404 Not Found — документ по указанному URL не существует.
• 405 Method Not Allowed — метод, используемый броузером, для данного URL не поддерживается.
• 406 Not Acceptable — ресурс, указанный клиентом по данному URL, существует, но не в том формате, который нужен броузеру.
• 407 Proxy Authentication Required — прокси-сервер должен санкционировать запрос перед тем, как пересылать его.
• 408 Request Time-out — броузер не передал полный запрос в течение установленного промежутка времени (который обычно задается в конфигурации сервера) и сервер разрывает сетевое соединение.
• 409 Conflict — данный запрос конфликтует с другим запросом или с конфигурацией сервера.
• 410 Gone — затребованный URL больше не существует и навсегда удален с сервера.
• 411 Length Required — сервер не примет запрос без указанного в нем заголовка Content-Length.
• 412 Precondition Failed — результат вычисления условия, заданного в запросе одним или несколькими заголовками if…, представляет собой значение «ложь».
• 413 Request Entity Too Large — сервер не будет обрабатывать запрос, потому что его тело слишком велико.
• 414 Request-URL Too Long — сервер не будет обрабатывать запрос, потому что его URL слишком длинный.
• 415 Unsupported Media Type — сервер не будет обрабатывать запрос, потому что его тело имеет неподдерживаемый формат.

Коды ответов в диапазоне 500-599 показывают, что сервер столкнулся с ошибкой и, вероятно, не сможет выполнить запрос броузера.

• 500 Internal Server Error — при обработке запроса на сервере один из его компонентов (например, CGI-программа) выдал аварийный отказ или столкнулся с ошибкой конфигурации.
• 501 Not Implemented — броузер запросил выполнение действия, которое сервер выполнить не может.
• 502 Bad Gateway — сервер (или прокси-сервер) получил недопустимые ответы другого сервера (или прокси-сервера).
• 503 Service Unavailable  этот код означает, что данная служба временно недоступна, но в будущем доступ к ней будет восстановлен.
• 504 Gateway Time-out — этот ответ похож на код 408 (Request Time-out), за исключением того, что лимит времени превысил шлюз или прокси-сервер.
• 505 HTTP Version not supported — сервер не поддерживает версию протокола HTTP, использованную в запросе.

Наиболее частой серверной ошибкой является отсутствие запрашиваемого ресурса (404 Not Found). Это может быть связано как с перемещением указанного ресурса, так и с указанием неверного URL-адреса.
Наполняя свою Web-страницу полезной информацией, вы не застрахованы от того, что какой-нибудь посетитель оставит где-то ссылку на конкретный файл вашего сайта. Сколько эта ссылка будет там храниться — никому не известно, но рано или поздно кто-то по ней обязательно придет, а вы к тому времени можете переместить требуемый файл куда угодно. Юзер, который хотел посетить вашу Веб страницу, получит лишь предупреждение об ошибке. Пользователь просто закроет страницу или перейдет на другой сайт. Так или иначе , этого посетителя вы, скорее всего, уже не сможете вернуть.

Однако Веб сервер Apache позволяет поменять стандартное сообщение об ошибке на свое собственное. В нем можно на родном языке, неудачливому визитёру сообщить, что интересующий его файл перемещен и следует начать его поиск с главной страницы сайта.

Делается это следующим образом. В корневом каталоге сайта помещается файл .htaccess. Если этого файла еще нет, то создайте его. В данный файл помещается команда следующего вида:

ErrorDocument 404
http://www.yousite.ru/error404.htm

Теперь в файл error404.htm поместите сообщение об ошибке 404, указав адрес главной страницы своего сайта и некоторый поясняющий текст.

Метки: Apache