C.7 Received body file
The HTTP body of data received from a web API is written to the received body file. This file is automatically created by the HTTP connection job. The format in which data is written differs depending on the specifications of the web API that was called.
If you include security information (such as a password) in this file, you do so on your own responsibility.
The following table describes the specifications of the received body file.
|
No. |
Definition |
Description |
|---|---|---|
|
1 |
Permission |
The access permission settings of the folder in which to create the received header file must permit the user who executes the job to create files. For the created file, the following permission settings are specified:
|
|
2 |
Character encoding |
Depends on the specifications of the web API to be called. |
|
3 |
Maximum size |
Specified by using the MaximumReceivedDataSize=maximum-size-of-receive-data entry in the connection configuration file. |
The received body file is created if you choose to output the header and body to different files for the receive data storage method in the definition items for HTTP connection jobs. If you choose to output the header and body to the same file, the body of received data is appended to the received header file. In this case, the received body file is not created.
- Supplementary notes
-
-
For HTTP connection jobs, whether the HTTP body is included in the received data is determined by the HTTP status code.
If the HTTP status code is 100 to 199, 204, or 304, the HTTP connection job does not create the received body file, assuming that the HTTP body is not included in the received data.
If the HTTP status code is other than the above codes, the HTTP connection job determines whether the HTTP body is included based on RFC2616. If the job determines that the HTTP body is not included, the received body file is not created.
-
If Y is specified for the TRANSFER_DECODING environment setting parameter, data received in chunk format is decoded when it is output. For details about the TRANSFER_DECODING environment setting parameter, see 20.14.2(1) TRANSFER_DECODING in the JP1/Automatic Job Management System 3 Configuration Guide.
-