Start of change

HTTP/1.1 compliance for CICS as an HTTP server

CICS® Web support now supports HTTP/1.1.

Releases of CICS before CICS Transaction Server for z/OS®, Version 3 Release 1 supported HTTP/1.0. CICS Web support is now enhanced to handle and provide features of the HTTP/1.1 specification, including chunked transfer-coding, pipelining, and persistent connections.

CICS Web support is conditionally compliant with the HTTP/1.1 specification, as described in the Internet Society and IETF (Internet Engineering Task Force) Request for Comments document RFC 2616, Hypertext Transfer Protocol - HTTP/1.1 (http://www.ietf.org/rfc/rfc2616.txt).

Conditional compliance with the HTTP/1.1 specification means that CICS satisfies all the "MUST" level requirements, but not all the "SHOULD" level requirements, that are detailed in the HTTP/1.1 specification, where these requirements are relevant to the functions actually provided by CICS itself. An implementation that satisfies all the MUST or REQUIRED level and all the SHOULD level requirements for its protocols is said to be unconditionally compliant. An implementation is not compliant if it fails to satisfy one or more of the MUST or REQUIRED level requirements for the protocols it implements.

There are three aspects to CICS Web support compliance with the HTTP/1.1 specification.
End of change