|
400
Bad Request
The server
did not understand your request. An improperly typed URL is usually the
cause. If not that, there could be a problem with the document itself.
401
Unauthorized
This URL
probably requires a username and password. Try submitting them again in
case you made an error. If the password doesn't seem to work, contact
the site administrator to resolve the problem.
402
Payment Required
This is
intended to return acceptable payment options. Not presently used.
403
Forbidden
You tried
to access a URL for which you don't have permission. If you usually can
access this document, there might be a problem with the server. If so,
contact the site administrator.
404
Not Found
This is
probably the most common status code. Your browser cannot locate the document
corresponding to the URL you entered. An improperly typed URL is usually
the cause. The document may also have been moved. If you cannot find it
elsewhere on the site, it may have been permanently removed.
405
Method Not Allowed
You may
be attempting to run a script that is not supported. Some ISPs do not
allow scripts on their servers, which could result in this status code.
For an explanation of methods in HTTP headers see this page of the HTTP/1.1
protocol
406
Not Acceptable
It’s
possible you have requested a page that contains files which your browser
has indicated to the server that it cannot accept, for example, a multimedia
file that your browser cannot process. Your browser sends information
about what files it can accept to the server (in the HTTP header) as part
of a request. You might check the preferences settings of your browser
to see if there are file types it is not accepting.
407
Proxy Authentication Required
There is
a proxy server between your client and the server you are requesting the
page from that requires a username and password.
408
Request Timeout
The request
took longer than allowed to complete. Try the request again. If this error
continues to appear, try waiting a few hours before repeating the request
409
Conflict
Conflicts
are likely to occur where an inappropriate alteration of the resource
is being attempted.
410
Gone
A 410 status
code is returned if the new address is altogether unavailable or the server
admin does not want to reveal it.
411
Length Required
Your client
did not define the length of the requested content in the request header.
412
Precondition Failed
The header
of the request specified information about acceptable files that is not
applicable to the requested file.
413
Request Entity Too Large
The content
of the request is more than the server can process. The request may have
included a message body, which is not always permissible.
414
Request-URL Too Long
Since a
POST request allows for an unlimited amount of data to be sent to a server
by tagging it on to the request, if the request were converted to a GET
request this error could result. Additionally, since a GET request allows
for appending of search or form data in the header, the URL created could
be longer than acceptable.
415
Unsupported Media Type
There may
have been an error in the MIME type indicated in the request header, i.e.,
your browser might have requested an image file, when in fact the requested
file is an application.
416
Requested Range Not Satisfiable
Your browser,
which sends information on acceptable file size as part of its request,
may have requested a file that does not fit these parameters. See the
HTTP protocol for more information.
417
Expectation Failed
The Expect
request-header field is used to indicate that particular server behaviors
are required by the client. The server could not execute these expectations.
|
![Wildfire Home Image [4k]](../../utility/home2.gif){kind=small}