HTTP response codes from the Web Gateway administration API
Status codes are returned in HTTP responses to requests made to the WebSphere® MQ File Transfer Edition Web Gateway administration API.
The header of a response returned
by the Web Gateway contains an HTTP response code. The HTTP header
in the following example contains the HTTP response code 200
OK:
The
following table describes the possible values for the HTTP response
code and some of the additional WebSphere MQ
File Transfer Edition error codes that can
be returned by the administration API: HTTP/1.1 200 OK
Server: WAS/6.0
Content-length: 0
HTTP response code | Example WebSphere MQ File Transfer Edition error codes | Example description |
---|---|---|
200 OK | None | A valid request has been handled correctly and optionally a response has been provided to the user. |
202 Accepted | None | A valid request has been handled correctly but WebSphere MQ File Transfer Edition does not guarantee that the requested action has completed. |
400 Bad Request | BFGWI0501 | The URI is not valid because it is missing an administration resource type. |
404 Not Found | BFGWI0515 | The requested resource cannot be found. For example, the file space does not exist. |
405 Method Not Allowed | BFGWI0516 | The requested resource does not support the
HTTP verb that has been used in the request. For example, a HEAD method is used on /admin/filespace/file_space_name/ and the only valid methods are POST, GET or DELETE. |
415 Unsupported Media Type | BFGWI0517 | An administration request has been received with a media type, specified by the Content-type HTTP header, that is not supported. For more information on the media types supported by the administration API, see the topic Content types for administering the Web Gateway |
500 Internal Server Error | BFGWI0018 | An internal error has been encountered when handling the request. An FFDC or ABEND file has been produced. |
502 Bad Gateway | BFGWI0019 | The request cannot be completed because an error occurred outside WebSphere MQ File Transfer Edition. For example, a WebSphere MQ queue manager is not available. |
503 Service Unavailable | BFGWI0020 | The destination is temporarily unavailable. For example, a WebSphere MQ queue is full. |
504 Gateway Timeout | BFGWI0021 | An attempt to complete the request has timed out because of time limits imposed by WebSphere MQ File Transfer Edition, or because of time limits imposed by the HTTP client. |
For information about additional WebSphere MQ File Transfer Edition error response codes that can be returned by the Web Gateway, see the topic Diagnostic messages.