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"?
Sadly this is an issue with the underlying Tomcat library and engineering has decided to not provide any work around, since the spec (RFC 7230) dictates that the reason-phrase should be ignored by the client.https://www.rfc-editor.org/rfc/rfc7230#section-3.1.2 A client SHOULD ignore the reason-phrase content.
Hi Mark, can you please email me directly regarding this? firstname.lastname@example.org. Thanks! JayMac
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, (and Jay)
Any tentative release date for CR04?
Were stuck on GW10.0 until we can solve this issue.
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.