September is beach season here in the Bay Area, and it looks like our release earlier this month got caught in a wash cycle. So, we’ve made a point release.
See below for details on the
util-slf4j-api dependency fix for the reason
why we decided to do a point release.
DefaultHeaderMap now validates HTTP Header names and
setUnsafe have been created to
allow adding and setting headers without validation. 3454f95d
finagle-core: Remove slow host detection from
finagle-core: When Finagle would exhaust a retry budget with an exception that was
FailureFlags, previously it would wrap that exception with a non-retryable
failure. This lead to surprising behavior for users. Those exceptions will no longer
be wrapped. 4ece3d2a
finagle-http: The finagle HTTP clients and servers now consider a
header to be a retryable nack. Servers will set this header when the response is
a retryable failure, and clients will interpret responses with this header as a