| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| 0.42.66 source code.tar.gz | 2026-08-25 | 4.9 MB | |
| 0.42.66 source code.zip | 2026-08-25 | 8.3 MB | |
| README.md | 2026-08-25 | 6.2 kB | |
| Totals: 3 Items | 13.2 MB | 0 | |
This is a minor maintenance release appropriate for all ServiceTalk users that contains several useful improvements and bug fixes. This release is expected to be a "drop-in" replacement for all prior 0.42.X releases.
# Changes
## Behavior Changes
- https://github.com/apple/servicetalk/commit/2fcff0db2549bf4eacf5f73ac7e4b36506505d73 - http: revised default aggregation limits and reworked how the warn-only mode introduced in
0.42.65 is configured (#3598)
- Defaults are now per role: clients warn at 64 MiB and are no longer planned to enforce by default; servers warn at 16 MiB and are still planned to enforce.
maxAggregatedPayloadSize(int)now selects the mode by sign: positive enforces (rejects), negative warns at its magnitude,0disables. The previous non-negative-only requirement is dropped.- The single
io.servicetalk.http.netty.temporaryDefaultMaxAggregatedPayloadSizesystem property is split into client- and server-specific properties; the original is kept as a deprecated fallback.
- https://github.com/apple/servicetalk/commit/d996a9d3efe80221b8f855499ab6ba45b0878f22 - serializer:
VarIntLengthStreamingSerializer/FixedLengthStreamingSerializernow accept a negativemaxMessageSizeas warn-only at its magnitude, matching the HTTP/gRPC sign convention above; previously all negative values were rejected (#3615)- Adds the permanent
io.servicetalk.serializer.utils.defaultMaxMessageSizesystem property; the previous...temporaryDefaultMaxMessageSizeis kept as a deprecated fallback.
- Adds the permanent
- https://github.com/apple/servicetalk/commit/ae0b12b51afb7352899745ea78b4c99d4ed488ee - the rate-limited warning for oversized HTTP/gRPC payloads now logs once every 2 hours instead of every 5 minutes (#3611)
- https://github.com/apple/servicetalk/commit/eeda1c5aaabc4764f871b3b699e1383b4f9f65aa - serializer: aligned the streaming serializers' warn interval (5 minutes -> 2 hours) and default warn threshold (4 MiB -> 16 MiB) with the HTTP/gRPC limiters above (#3612)
## Bug Fixes
- https://github.com/apple/servicetalk/commit/0544b63e6d1091974dc6e07b2d43fdec671942fd - http-netty: the HTTP/2
:pathpseudo-header is now validated as non-empty, VCHAR-only per RFC 9113 §8.3.1; an illegal:path(e.g. containing CR, LF, NUL, or space) could previously reach the service and be re-emitted on an HTTP/1.1 downgrade (#3599)- A raw non-ASCII request-target now fails instead of being silently corrupted by HPACK; use
path(String)orrequestTarget(String, Charset)to percent-encode.
- A raw non-ASCII request-target now fails instead of being silently corrupted by HPACK; use
- https://github.com/apple/servicetalk/commit/2286e02a43d961dbc1b04217befe33d2e18f75ff - loadbalancer: fixed a negative host index in the weighted
RoundRobinSelectoronce the shared selection counter passed 2^31, which threwArrayIndexOutOfBoundsException(#3588) - https://github.com/apple/servicetalk/commit/c2c1fe78c6e34722540708f94f9881dfabaab8d3 - grpc: interrupting a blocking gRPC call now cancels the in-flight operation and restores the thread's interrupt status; failures also now propagate as the unwrapped cause (e.g.
GrpcStatusException) instead of a wrappingExecutionException(#3597, [#3574])- Adds a new public
io.servicetalk.concurrent.api.BlockingUtilswizhblockingInvocation(Single)/blockingInvocation(Completable); theconcurrent-api-internalequivalent is now deprecated in its favor.
- Adds a new public
- https://github.com/apple/servicetalk/commit/51ed14aee9c8ec769165493e8e2fb00df95eb591 - concurrent-api: fixed an integer overflow when sizing
FromInputStreamPublisher's read buffer that could throwNegativeArraySizeException(#3587) - https://github.com/apple/servicetalk/commit/c52184afab4f57ca863d936e2c08cd65c2642d46 - loadbalancer:
OutlierDetectorConfig's copy constructor now preservesewmaCancellationPenalty,ewmaErrorPenalty,concurrentRequestPenalty, andcancellationIsErrorinstead of silently resetting them to defaults; several load balancer builder javadocs were also corrected to match actual behavior (#3604) - https://github.com/apple/servicetalk/commit/db6f880fb9a55008d5303b7d9e2c93890c533c58 - opentracing-log4j2: switched provider registration to
ServiceLoader, sincelog4j-provider.propertiesis no longer honored as of log4j 2.24.x (#3592)
## Dependencies
- https://github.com/apple/servicetalk/commit/691dc3b24bf035fa9283ce25b08ffc9ff974c917 - Update Netty 4.1.136 -> 4.2.17 (#3586)
- Adds
io_uringas a transitive dependency for all users. ServiceTalk continues to compile against, and remain runtime-compatible with, Netty 4.1.x.
- Adds
- https://github.com/apple/servicetalk/commit/2b8062c2dbe3ffaec8d932644e63147e56f031b9 - Update log4j 2.23.1 -> 2.24.3 (#3593)
- https://github.com/apple/servicetalk/commit/f346bb8e7a88f230ddf60ab9438229e6477c8dc5 - Update Jackson 2.19.4 -> 2.21.5
- https://github.com/apple/servicetalk/commit/b8c2a03ffaf29b349cbf9cbc940eb18dddbec6ae - Update Jackson3 3.1.1 -> 3.1.5
- https://github.com/apple/servicetalk/commit/3ee71fc8624fbfafd6057adfa70cd4c1007f3889 - Update Jersey 2.41 -> 2.47
- https://github.com/apple/servicetalk/commit/b0c23c2c9693c7668e0773ca3c0be550bdef0120 - Update Jersey 3.1 Jakarta EE 10 dependencies (
jaxb-api4.0.4 -> 4.0.5,jaxb-core/jaxb-impl4.0.6 -> 4.0.9,jersey33.1.11 -> 3.1.12) - https://github.com/apple/servicetalk/commit/845f1552e9c890bc2a131e9ea6e719c386da35d2 - Update jctools 4.0.5 -> 4.0.6
- https://github.com/apple/servicetalk/commit/5d30a9aedc476f16ddbc8bb07cef1b3e0f527c97 - Update protobuf 3.25.8 -> 3.25.9
- https://github.com/apple/servicetalk/commit/ee764055e1ea904697526fe1b061bee5ac91c2af - Update proto-google-common-protos 2.51.0 -> 2.63.1
## Documentation
- https://github.com/apple/servicetalk/commit/cd98f0325948f20b8598807a06034a6b6b796a31 - examples: added a mutual-TLS HTTP CONNECT proxy example demonstrating layered TLS through a CONNECT proxy (#3607)
# Thank you Every idea, review, and bug-report counts and so we thought it is worth mentioning those who helped in this area. Please report any unintended omission.
@n200534 @arnabnandy7 @bryce-anderson @chrisvest @idelpivnitskiy @daschl