Share via

2.2.1.6.2 HTTP Responses

  • Article

The response is collected in the server and sent to the client in one or more chunks, depending on the response size and the HTTP configuration options. Depending on the size of the response body and the HTTP configuration, the response can be one of the following cases:

CASE 1: A binary package with no length specified.

The binary package is wrapped in an HTTP response that explicitly closes the connection, and all bytes in the transmission are considered part of the response. See section 4.1.1 for an example.

CASE 2: A binary package of defined length.

The Data Pump component uses chunked transfer encoding. For more information about this encoding, see [RFC2616]. In this case the connection is not explicitly closed. Subsequent chunks are identified as being part of the same response by use of the Transfer-Encoding field. See section 4.1.2 for an example.

CASE 3: An error.

The error is encapsulated as an HTTP header, as specified in section 2.2.1.6.2.1.4.

The requirements for each case are specified in section 2.2.1.6.2.1.1.6.