You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the transformation filter will fail parsing the body because it's not a JSON...when it fails the response_code_details is never changed from the upstream.
For example. When calling httpbin.org/xlm . It will return a 200 response code and a "response_code_details":"via_upstream" however when we add the Transformation Filter and it tries to parse the the body it fails:
The response_code_details should be change to something instead of via_upstream which might cause inaccurate assumption that the upstream returned the 400. Especially since the error line:
2024-12-11T15:48:35.521006Z debug envoy filter external/envoy_gloo/source/extensions/filters/http/transformation/transformation_filter.cc:276 [Tags: "ConnectionId":"1144","StreamId":"651067811395905973"] failure transforming [json.exception.parse_error.101] parse error at line 1, column 1: syntax error while parsing value - invalid literal; last read: '<' thread=21
is a debug line and when debug isn't enabled on the envoy...we never see any error condition.
The text was updated successfully, but these errors were encountered:
Sometimes the transformation filter will fail parsing the body because it's not a JSON...when it fails the
response_code_details
is never changed from the upstream.For example. When calling httpbin.org/xlm . It will return a 200 response code and a
"response_code_details":"via_upstream"
however when we add the Transformation Filter and it tries to parse the the body it fails:The access log has
"response_code_details": "via_upstream",
and"response_code": 400
The
response_code_details
should be change to something instead ofvia_upstream
which might cause inaccurate assumption that the upstream returned the 400. Especially since the error line:is a debug line and when debug isn't enabled on the envoy...we never see any error condition.
The text was updated successfully, but these errors were encountered: