Release notes for packages.
Unary POST and Connect GET now return consistent Connect errors and preserve error metadata. Connect GET also validates decoded requests. Validation failures and unexpected handler exceptions reach the application's Ktor StatusPages configuration so applications can choose their responses.
Server-streaming RPCs (rpc X(Req) returns (stream Res)) are now served end to end.
The code generator emits handlers that return a cold Flow<Res>, and
handleServerStream writes each emitted message as an envelope frame followed by an
end-of-stream frame. Response headers are flushed before the first message, a
ConnectException thrown by the flow becomes the end-of-stream error, and trailers can
be set through the new call.connectResponseTrailers(). When a client disconnects, the
handler's flow collector is cancelled instead of the failure being swallowed.
Services with server-streaming methods in their .proto will see a new member on the
generated handler interface — those methods used to be skipped by the generator.
Connect-Ktor now generates and serves bidirectional-streaming RPCs. Half-duplex calls work on CIO and Netty, while Netty over HTTP/2 supports full-duplex request and response interleaving.
Generated handlers accept a Flow<Req> and return a Flow<Res>. The streaming path
handles envelope framing, request validation, per-message size limits, headers, trailers,
deadlines, and cancellation.
Install ConnectStreaming on a Ktor route to configure maxMessageSize for
client, server, and bidirectional streaming request messages. Child routes can
override the setting; explicit handler limits take precedence. Without the plugin,
the limit remains 4 MiB. Unary request limits and generated source are unchanged.
Recompile existing generated source against the updated library to use the plugin.
Idempotent unary RPCs (protobuf NO_SIDE_EFFECTS) can now be served over HTTP GET
with the Connect query-parameter encoding. The code generator emits GET routes for
eligible methods, and custom JSON strategies (for example TypeRegistry for
google.protobuf.Any) can be registered via installConnectGetCodecs.
Route.connectBodyLimit(maxBytes) enforces a maximum inbound message size for
unary Connect RPCs and returns resource_exhausted when the limit is exceeded.
Compressed requests are measured after decompression so gzip bombs cannot bypass
the cap.
Unary Connect RPCs negotiate request compression through Ktor's Compression plugin.
UnaryCompressionGuard validates Content-Encoding before the body is read and
rejects unsupported encodings with Code.UNIMPLEMENTED.