This release is mostly bug fixes but also reconciles connect-go with recent updates to the specification regarding mapping of RPC error codes to/from HTTP status codes (see connectrpc RFC 003)
What's Changed
Enhancements
- Only send a grpc-status-details-bin trailer in the gRPC protocol if the error has details by @bhollis in #713
Bugfixes
- Fix
ErrorWriter IsSupportedcheck to report false on ambiguous content-type and options indicate connect protocol version header is required by @emcfarlane in #700 - In Connect unary protocol, fallback to code based on HTTP status if unable to deserialize code from JSON body by @jhump in #702
- Fix
ErrorWriterto recognize protocols, even if content-type indicates unrecognized codec by @emcfarlane in #701 - Fix some places in the framework that weren't correctly recognizing and returning context-based error code (e.g. "canceled" or "deadline_exceeded") by @jhump in #709
- Use "unimplemented" code for stream cardinality violations by @jhump in #712
- Restrict which metadata in an error can be propagated into response metadata by @emcfarlane in #711
Other changes
- Revise RPC error code <-> HTTP status code mappings per latest changes to the spec by @jhump in #706
New Contributors
Full Changelog: v1.15.0...v1.16.0