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
We found an issue when testing the fix of #10801. When a service responds with a message with all default value fields, the JSON response would be totally empty.
The reason for this issue is that we assume a message to be at least of length 1 when unframing.
Removing this restriction (a message can be of length 0) fixes this issue.
Fix FTI-5054Fix#10802
Is there an existing issue for this?
Kong version (
$ kong version
)*
Current Behavior
When a gRPC service returns an empty array, it's encoded as
{}
in the JSON body.Expected Behavior
It should be encoded as
[]
.Steps To Reproduce
res:read_body()
would return something like{ "array": {}, "nullable": "ahaha"}
.Anything else?
This issue is created for visibility for an internal ticket(FTI-5002).
The text was updated successfully, but these errors were encountered: