Table of Contents
Advertisement
200 Series
v 200 - OK
v 201 - Created
v 202 - Accepted
v 203 - Non-Authoritative Information
v 204 - No Content
v 206 - Partial Content
300 Series
v 301 - Moved Permanently
v 302 - Moved Temporarily
400 Series
v 400 - Bad Request
v 401 - Unauthorized
v 402 - Payment Required
v 403 - Forbidden
v 404 - Not Found
94
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
Successful transmission. This is not an error.
The request has been fulfilled and resulted in the creation of a new resource. The
newly created resource can be referenced by the URLs returned in the
URL-header field of the response, with the most specific URL for the resource
given by a Location header field.
The request has been accepted for processing, but the processing has not yet
completed.
The returned META information in the Entity-Header is not the definitive set as
available from the origin server, but is gathered from a local or vendor-acquired
copy.
The server has fulfilled the request, but there is no new information to send
back.
You requested a range of bytes in the file, and here they are. This is new in
HTTP 1.1
The requested resource has been assigned a new permanent URL and any future
references to this resource should be done using one of the returned URLs.
The requested resource resides temporarily under a new URL. Redirection to a
new URL. The original page has moved. This is not an error; most browsers
invisibly fetch the new page when they see this result.
The request might not be understood by the server because it has a malformed
syntax. Bad request was made by the client.
The request requires user authentication. The response must include a
WWW-Authenticate header field containing a challenge applicable to the
requested source. The user asked for a document but did not provide a valid
user name or password.
This code is not currently supported, but is reserved for future use.
The server understood the request but is refusing to perform the request because
of an unspecified reason. Access is explicitly denied to this document. (This
might happen because the web server doesn't have read permission for the file
you're requesting.) The server refuses to send you this file. Maybe permission
has been explicitly turned off.
Advertisement
Table of Contents
