HTTP response codes
Status codes are returned in HTTP responses to requests made to the WebSphere® MQ File Transfer Edition Web Gateway.
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 an example of an associated WebSphere MQ
File Transfer Edition error code that can be
returned. For more information about the WebSphere MQ
File Transfer Edition error codes, see Diagnostic messages.HTTP/1.1 200 OK
Server: WAS/6.0
Content-length: 0
HTTP response code | Example WebSphere MQ File Transfer Edition error code | 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. For example, a file upload transfer request has been handled and submitted to a WebSphere MQ File Transfer Edition agent but the transfer has not yet taken place. |
400 Bad Request | BFGWI0001 | The URI is not valid because it is missing a resource type. |
403 Forbidden | BFGWI0056 | There is no WebSphere MQ Message Descriptor (MQMD) user identifier defined for the user. |
404 Not Found | BFGWI0015 | The requested resource cannot be found. |
405 Method Not Allowed | BFGWI0016 | The requested resource does not support the
HTTP verb that has been used in the request. For example, a GET has been used against a resource that only allows POST or DELETE. |
410 Resource Gone | BFGWI0031 | The requested resource is no longer available. For example, the requested file has been deleted from the file space. |
413 Request Entity Too Large | BFGWI0026 | The request contains a file that is too large to be handled by the server. |
415 Unsupported Media Type | BFGWI0017 | A request has been received with a media type, specified by the Content-type HTTP header, that is not supported. |
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. |