How to set up HTTP Connection header

[SIDDHARTHJAISWAL]

Hi,

 

 I am setting up "connection" and "server" #httpheaders to "keep-alive" and "API Gateway" respectively for certain port (8080)  as described in document How to change the Server Header from "Apache-Coyote/1.1" with the CA API Management Gateway. 

 

However in response , "server" header is reflecting changed value but "connection" header value remains "close". Please note that value of cluster property #io.httpDisableKeepAlive is set to "false"

 

Please let me know is there any other setting required to make connection as #keep-alive rather than getting closed after every request. Attached herewith is the doc containing screen shots.

 

Thanks,

Siddharth

Attachment(s)

ConnectuionHeaderSettingIssue.docx   308 KB 1 version

[DustinDauncey]

Hello,

 

There is no "connection" property in this case, which is why this is not working the way you are expecting. These advanced properties are specific to the configuration of Tomcat, an API Gateway dependency for HTTP connections. The available properties for Tomcat are documented here, but there is not one for setting the connection type since these are more for Tomcat operations than a HTTP header-level property: Apache Tomcat Configuration Reference - The HTTP Connector 

 

If you want to modify headers in policy, I believe you can use the "Manage Transport Properties / Headers Assertion, which is documented here: Manage Transport Properties/Headers Assertion - CA API Gateway - 9.2 - CA Technologies Documentation 

 

I hope the above helps clarify the reason behind the behaviour and how to achieve what you are wanting.

 

If there is anything else I can do for you on this matter, please do not hesitate to reply to this response. If you feel this matter has been resolved to your satisfaction, please be sure to mark this response as one that "resolved" this post.

 

Sincerely,

 

Dustin Dauncey

Sr Support Engineer, Global Customer Success

Email: [e-mail]

Phone: [phone] ,48385

Phone if outside North America - https://tinyurl.com/CAContactSupport

CA API Management Community: https://tinyurl.com/CAAPIMCommunity

[SIDDHARTHJAISWAL]

Hi,

 

 Can you please let me know if there is any way to make HTTP connections to/from Gateway as Keep Alive ?

 

Thanks,

Siddharth

[SIDDHARTHJAISWAL]

Hi,

 

Our gateway's HTTP version is 1.1. As per RFC7320 (RFC 7230 - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing   ), HTTP1.1 should support persistent connection by default. However, despite of not explicitly setting up Connection header in properties, I am getting Connection as "close" in response, which shows that my HTTP1.1 browser client (postman) is unable to establish persistent connection. Does Gateway 9.0 supports persistent connection at all?

 

Thanks,

Siddharth

[didsi01]

Persistent connection issue has been resolved through support case. return template response assertion had send response immediately checked, by doing so it will disable keep alive. Unchecking it fixed the issue.