Gorouter Returns wrong HTTP response code to client when the request flow uses HTTP 100-continue

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Gorouter sends the wrong HTTP response to clients when the request workflow uses an HTTP 100-continue response (and possibly other 1xx interim response messages). After the 1xx code, the gorouter ALWAYS returns an HTTP 200, rather than the response code sent by the app/backend. This affects Gorouter version 0.293.0 and newer. The following releases of TAS and IST are impacted by this regression.

Tanzu Application Service Tile ( TAS ) 

• 6.0.0 - 6.0.3
• 5.0.10 - 5.0.13
• 4.0.20 - 4.0.23
• 2.13.37 - 2.13.39
• 2.11.55 - 2.11.57

TAS Isolation Segment Tile ( IST )

• 6.0.0 - 6.0.3
• 5.0.10 - 5.0.13
• 4.0.20 - 4.0.23
• 2.13.34 - 2.13.36
• 2.11.49 - 2.11.51

Resolution

A fix has been committed, however the fix has yet to be released in a patched version of TAS or IST.  This is fixed in routing release v0.297.0 and the TAS release notes should include the following.

• Fixes an issue with gorouter where the incorrect HTTP response codes would be sent for request workflows using 100 Continue responses. Status codes were returned as 200 OK, regardless of what the backend app provided.

This KB will be updated when the fixed TAS versions are confirmed.