10.1 CR4 ETA is 11/30/23 (subject to change). Note, this problem is not in 10.1 GA. It was first introduced in 10.1 CR1 when we upgraded Tomcat.
Original Message:
Sent: May 02, 2023 09:26 AM
From: Mark Stewart
Subject: Change in HTTP response string that may affect load balancer availability tests (v10.1)
Ben, (and Jay)
Excellent news.
Any tentative release date for CR04?
Were stuck on GW10.0 until we can solve this issue.
Original Message:
Sent: May 01, 2023 10:37 AM
From: Ben Urbanski
Subject: Change in HTTP response string that may affect load balancer availability tests (v10.1)
Hello Jay, Mark, and others,
We have decided to address this issue by customizing Tomcat to support optionally returning the HTTP response reason phrase on a per HTTP listener basis. We're currently planning to deliver this enhancement in our upcoming 10.1 CR4 and 11.0 CR2 releases (subject to change).
------------------------------
Ben Urbanski
Product Manager, API Gateway
Layer7 API Management
Original Message:
Sent: Apr 27, 2023 01:46 PM
From: Mark Stewart
Subject: Change in HTTP response string that may affect load balancer availability tests (v10.1)
Jay,
We are experiencing a similar situation with http Response string change in GW10.1.
Is there a work-around or flag we can set to re-enable the full http status return code?
For us the issue is around httpstatus 404.
Before the update we had httpstatus return "404 Not Found"
Now on 10.1 CR03 we get just "404" w/o "Not Found".
This is tripping up some outside vendor code that is relying on the entire "404 Not Found" string.
We are not in control of this back end vendor code.
Additionally there may be other vendors effected as well. We recently saw this in our test environment.
We are holding off on PROD deployment of GW10.1 CR03 install until we can figure out this issue and a couple other minor problems.
Any possibility to get the gateway to pass the entire http status return "404 Not Found"?
Original Message:
Sent: Feb 14, 2022 02:04 PM
From: Jay MacDonald
Subject: Change in HTTP response string that may affect load balancer availability tests (v10.1)
Hello API Gateway Community,
I recently ran into an issue where an F5 load balancer was hitting a service on the API Gateway to check availability of the node and it stopped working after the upgrade to v10.1. This turned out to be due to a change in the format of the response from the Gateway (resulting from an underlying library change). Prior to 10.1 the Gateway would return "HTTP 200 OK" as the first line of the response header. As of 10.1 it turns out that some situations will NOT include the "OK" string in the header and only return "HTTP 200". If your load balancer is configured to check for the OK string in that response header you will need to modify the rule to not do so and only check for the 200 status code.
------------------------------
Jay MacDonald - Adoption Architect - Broadcom API Management (Layer 7)
------------------------------