API Gateway HTTP Response status missing OK or Reason Phrase on API Gateway 10.1 CR01

Products

• CA API Gateway

Issue/Introduction

API Gateway 10.1 Cr01 to 10.1 Cr03 have a different behavior in HTTP status response when compared with the previous versions and newer versions. The http status code was present but no reason phrase like OK. Apps should not depend on this reason phrase but some apps may.

Environment

CA API Gateway 10.1 CR01 - 10.1 CR03

Resolution

Prior to GW 10.1 CR1, the Gateway response would send an HTTP Response Message that contained a status line comprised of the following values:

status-line = HTTP-version SP status-code SP reason-phrase CRLF (Example: HTTP/1.1 200 OK).

Starting Gateway 10.1 CR1  the reason phrase is no longer included based on the following RFC 7230#section-3.1.2 comments:

• The first line of a response message is the status-line, consisting of the protocol version, a space (SP), the status code, another space, a possibly empty textual phrase describing the status code, and ending with CRLF.
• A client SHOULD ignore the reason-phrase content.

As noted in the RFC, the client should not expect this reason phrase as a result the latest HTTP libraries removed this reason phrase.

As of Gateway 10.1 CR04 this reason Phrase was added back for compliance with legacy applications.

To re-enable the reason phrase in response in Gateway 10.0 CR4 and later, you must add the advanced property sendReasonPhrase=true for a listen port you want it to be enabled on.

Additional Information

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/10-1/release-notes/new-features-and-enhancements.html#concept.dita_newfeatures_refresh_gw10cr2_addendum