The Gateway Client (transaction /IWFND/GW_CLIENT) for SAP Gateway is a powerful tool that enhances the existing Error Log.
It allows you to reproduce the exact runtime situation that led to a particular error.
In such cases, you can launch the Gateway Client from the Error Log context screen to replay all the steps that led to the error.
HTTP Requests
The Gateway Client enables you to test different HTTP requests. To test an HTTP request, proceed as follows:
- Select HTTP method (GET,POST,DELETE,HEAD,PUT,PATCH,MERGE).
- Enter request URI.
OR
Upload the service data (e.g. local file) to the HTTP Request frame by choosing the "Add file" button.
The preview of the HTTP request file will be displayed below. - Execute (F8).
- Gateway Client displays the HTTP response.
HTML Status Code
The test URL execution can returns different HTML status codes.The following table contains all of the possible response codes:
Successful
| Status code | Description |
|---|---|
| 200 | OK - The request was successful. |
| 201 | Created - The request has been fulfilled and resulted in a new resource being created. |
| 202 | Accepted - The request has been accepted for processing, but the processing has not been completed. |
| 204 | No Content - The server has fulfilled the request but does not need to return an entity-body, and might want to return updated meta information. |
Client Error
| Status code | Description |
|---|---|
| 400 | Bad Request - The request could not be understood by the server due to malformed syntax. GET: Resource not found |
| 401 | Unauthorized - The request requires user authentication. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. |
| 403 | Forbidden - The server understood the request, but is refusing to fulfill it. The user does not have the authorization and the request should not be repeated. e.g.: No authorization to access service |
| 404 | Not Found - The server has not found anything matching the Request URI. No indication is given of whether the condition is temporary or permanent. The data you wanted to receive does not exist in the database. |
| 405 | Method Not Allowed - The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response must include an Allow header containing a list of valid methods for the requested resource. |
| 408 | Request Timeout - The client did not produce a request within the time that the server was prepared to wait. |
| 412 | Precondition Failed - The precondition given in one or more of the request-header fields evaluated to be false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended. |
| 415 | Unsupported Media Type - The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. |
Server Error
| Status Code | Description |
|---|---|
| 500 | Internal Server Error - The server encountered an unexpected condition which prevented it from fulfilling the request. |
| 502 | Bad Gateway - The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. |
| 503 | Service Unavailable - The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. |
| 504 | Gateway Timeout - The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request. |