Support Inbound HTTP Request Body decompression in z/TPF HTTP Server for REST API or application logic

Enhancement to the z/TPF HTTP server to natively support decompression of inbound HTTP request bodies when the Content-Encoding header is set to gzip or deflate. The implementation should leverage existing z/TPF hardware‑accelerated compression capabilities.

This enhancement would allow compressed request payloads to be transparently decompressed by the server before being passed to REST frameworks or application logic, saving network bandwidth.

Currently, the z/TPF HTTP server supports compression only for outbound HTTP responses. When a client sends a compressed HTTP request body (for example, Content-Encoding: gzip), the server does not automatically decompress the payload. Instead, the compressed bytes are passed directly to the application layer.

Requested Enhancement

Enhance the z/TPF HTTP server to:

1. Automatically detect inbound compression using standard HTTP headers:

   • Content-Encoding: gzip

   • Content-Encoding: deflate

2. Decompress inbound HTTP request bodies at the server level before passing the payload to the REST framework or application logic.

3. Leverage existing z/TPF compression infrastructure, including:

   • zlib integration

   • Hardware acceleration via where available

4. Deliver the decompressed payload transparently to:

   • Existing REST services

   • DFDL‑based interfaces

   • Applications

Without requiring code changes.

Use Case Example

• REST‑style POST APIs receiving large operational datasets (for example, flight operational data)

• Clients already support standard HTTP compression and expect transparent server‑side handling

• High‑request‑volume environments where bandwidth efficiency is critical