This release contains backports for a number of relevant changes for the 10.1.x branch.
- Collision-resistant hashMap fixes #2343
- TLS closing issue fixes #2344
- Compilation error with Scala 2.12 #2350
- Dependency upgrades #2342
This release fixes the DoS vulnerability in the
decodeRequest directive. Please update as soon as possible.
To avoid excessive memory usage we introduced two new limits that apply per default:
akka.http.routing.decode-max-size: This limit applies when you use
decodeRequestto limit the amount of decompressed data. The default limit is 8 megabytes.
akka.http.parsing.max-to-strict-bytes: This limit applies when you use
toStrictEntitydirective (and related directives). It will only collect up to the given amount data and fail otherwise. The default limit is 8 megabytes.
Depending on your application requirements, you may want to change these settings.
- Restrict the maximum size of a request entity after uncompressing it with
- Restrict the maximum size of a request entity when reading it into memory with
- Support parameters for custom media types (#2005)
This release adds the long awaited akka-http-caching module inspired by spray-caching.
It also features a new implementation of the client pool infrastructure. This will allow us in the future to finally tackle many of the issues reported for the existing infrastructure like request timeouts, handling unread response entities, and other issues more easily.
In an ongoing behind-the-scenes effort, @jonas, @jlprat and others continued to improve the structure of our documentation to consolidate Java and Scala documentation. This reduction in duplication of documentation content will allow us to make changes to the documentation more easily in the future. Thanks a lot!
In a several month long effort members from the community and the Akka team discussed and implemented the long-awaited replacement of spray-caching. The new module
akka-http-caching got quite an overhaul over spray-caching and is now backed by caffeine.
The caching API is currently marked with
@ApiMayChange and thus may change based on feedback from real world usage. Some improvements are already planned to make it into future releases. We hope further collaboration within the community will help us stabilize the API.
See the documentation for more information.
The existing host connection pool infrastructure has accrued quite a lot of issues that are hard to fix. Therefore, we decided to rewrite the old version which was based on a stream graph jungle with a new version implemented as a single GraphStageGraphStage which will be easier to maintain. The new infrastructure already passes all the old tests and is now considered ready to be tested. The new implementation can be enabled with the feature flag
akka.http.host-connection-pool.pool-implementation = new. One important feature that is available only with the new pool implementation is a new warning that will be shown if user code forgets to read or discard a response entity in time (which is one of the most prominent usage problems with our client API). If you experienced problems with the old implementation, please try out the new implementation and report any issues you find.
We hope to stabilize the new implementation as soon as possible and are going to make it the default in a future version.
To clean up internal code, we made a few incompatible changes to classes that were previously kept public accidentally. We now made those classes private and marked them as
@InternalApi. Affected classes are
akka.http.scaladsl.coding.GzipCompressor. The actual codec APIs,
Deflate, are not affected. This is in violation with a strict reading of our binary compatibility guidelines. We still made that change for pragmatic reasons because we believe that it is unlikely that these classes have been used or extended by third parties. If this assumption turns out to be too optimistic and integration with third-party code breaks because of this, please let us know.
Several APIs in
Http previously required an implicit
Materializer argument (explicit in the Java version) where it was not necessary. In #1464, we added new entry points without the implicit materializer. The old versions were kept as
private[http] which makes this a binary compatible change. However, if you used to pass in a materializer explicitly, compiling the code will now fail. In that case, you can just remove the explicitly passed-in materializer argument.
- New host connection pool infrastructure (#1312)
- Allow disabling of parsing to modeled headers (#1550)
- Convert RFC references in documents in model classes to scaladoc (#1514)
- Allow configuration of default http and https ports (#1449)
- Remove unnecessary implicit
materializerparameter in several top-level HttpHttpHttpHttp entry point APIs (#1464)
X-Forwarded-Hostheader models (#1377)
- Lookup predefined header parsers as early as possible (#1424)
- Add multiple file upload directive (#1033)
- Add Marshaller.oneOf(m1, m2) to JavaDSL (#1551)
- Improve performance of LineParser for SSE unmarshalling (#1508)
- Automatically probing and decompression support for zlib wrapped deflate streams (#1359)
- Simplify implicit parameter structure in FormFieldDirectives (#541)
- Return BadRequest when size of FormData exceeds limit of
- Provide Dilated Timeouts for Java Testkit (#1271)
- Add more comprehensive description of the TestRoute run methods (#1148)
- Add a runWithRejections method to the Java TestRoute API (#1148)
- Support separation of route execution from checking in the Java DSL (#1148)
- New module partly ported from spray-caching backed by caffeine (#213)
- Ongoing work on consolidating Java and Scala documentation (#1290)
- Update Paradox and docs to use new features (#1436)
- Update to sbt 1.0.x
- Fix userinfo parsing to percent decode input in UriParser (#1558)
- Remove duplicate settings from akka.http.host-connection-pool.client so that akka.http.client will be picked up by default (#1492)
- Add minConnections modifier to javadsl ConnectionPoolSettings (#1525)
- Fix race condition in WebSocket switch leading to broken websocket connections in tests (#1515)
- Mark coding implementation classes as internal API (#1570)
It is now possible to connect to HTTP(S) Proxies that require an authorization via an
Proxy-Authorization header. This can be set up directly on the ClientTransportClientTransport object when configuring the proxy. (#1213)
Behind the scenes, a lot of work has been done on the ongoing effort to consolidate the Java and Scala versions of the documentation, notably by Jonas Fonseca and Josep Prat. This will make our documentation more consistent, higher-quality and more easy to browse and maintain (#1290)
- (server) Better error reporting when failing to handle CONNECT requests (#1315)
- Add HttpApp.startServer(host, port, system) (#1294)
- Preserve the order of repeated parameters when retrieving query string as a multimap (#1270)
- Missing final boundary for empty multipart entities (#1257)
- Add Cache-Control ‘immutable’ value (#1212)
- Http2: Inbound flow control (#737)
- HttpChallenge rendering is broken if realm parameter is None (#1295)
- Logging with println in Http2ServerDemux (#1275)
- Incorrect request URIs with HTTP/2 (#1274)
- HttpResponseParser returns invalid status code for statuses without reason phrase (#1251)
- Ensure that no responses are lost when
host-connection-pool.idle-timeoutkicks in (#1245)
- Large response entity is truncated over https with ‘Connection: close’ header (#1219)
This release fixes a regression in 10.0.8 that occurred when using media ranges and connecting to a HTTP server that fails to specify the charset in the
Additionally, support for HTTP status code 418 has been introduced #1206
Support for proxies that require authentication is yet to be implemented and is tracked by the ticket #1213
Akka-http has a strongly typed media type / content type system, and knows at compile time about which media types are supposed to express a character set attribute, e.g.
text/plain; charset=UTF-8. Before this release, akka would silently assume UTF-8 for
ContentType instances of media types with a missing
From now on, content types missing a charset can be both parsed and expressed directly, using the new
- For incoming Content-Type headers with values missing a charset, such as
text/plain, the header
ContentTypewill be represented as
WithMissingCharset, rather than assuming an UTF-8 charset (which could have been a wrong guess).
- If you need to create such a content type programmatically, use e.g.
Note to scala users: If you have
match statements across
ContentType, keep an eye out for new compiler hints. You need to decide what what to do in case you get a content type with a missing character set, by adding a
Support for Server-Sent events was added by merging akka-sse project by @hseeberger. Thank you very much, Heiko!
- Add support for Server-Sent Events (#669)
- Add support for textual content types with missing character set (#1134)
- Remove unnecessary dependency to ScalaTest from JUnitSuiteLike (#1147)
- Document pluggable client transport infrastructure and HTTP(S) proxy support (#192)
- Reference security announcements and release notes in ToC (#1199)
- Parse Websocket headers according to the set header processing mode (#1166)
- Fix a regression which caused the idle-timeout on server side not to function properly (#1012)
- Add a special handling of the charset parameter in Accept header when comparing media types (#1139)
- Use ws(s) scheme instead of http(s) when calculating effective websocket request URIs (#909)
We prepared new seed templates for starting out with Akka HTTP using the Java DSL as well as Scala DSL. By using the
sbt new command one can now easily get a small sample project to easily get started with your first Akka HTTP app. More instructions on the seed template pages.
Akka HTTP treats differently by default a route that ends with slash (
/) than one that doesn’t. From this version on, users who don’t want to have this distinction, can use a new Path Directive called
ignoreTrailingSlash. This route, will retry its inner route with and without a trailing slash. If you want to know more about this feature, please check the documentation page.
- Added new Path Directive
- Prepared new seed templates for Akka HTTP apps (for both Java DSL and Scala DSL) (1137 & 1055)
- Migrated to the new docs theme (same as Akka) (#1129)
HttpApp#routemethod was renamed to
routesto highlight it is “all the routes” (#953)
- Synthetic Remote-Address header setting is now honored in HTTP2 server blueprint (#1088)
- OSGi Import-Package ranges have been fixed to allow Akka 2.5.x (#1097)
- Dates in RFC1123 format with single-digit-day are now properly parsed (#1110)
10.0.6 is a security and maintenance release in the stable 10.0.x series of Akka HTTP.
This release contains a fix for a serious security vulnerability that allows a remote attacker to shut down any Akka HTTP application using the routing DSL. See the details for more information. Please update as soon as possible.
- Make response parser more relaxed on accepting status line without reason message (#981)
- Use media type parameters in content negotiation (#963)
- Small performance improvements (#999, #1032)
- Allow binding server with HTTP/2 support via configuration flag with
- Make marshaller composition more lazy to prevent redundant marshalling when using
- Allow Java-implemented ContentTypeResolver (#360)
- Java DSL routing
completenow has override that takes@unidoc[ResponseEntity] as a parameter instead of RequestEntityRequestEntity)
- Improved usage and documentation of Encoder / Decoder on the Scala and Java side (#771)
- Refactoring: move handling of per-stream frames to dedicated state handlers (#1064)
- Provide Decoding Response example for Java (#760)
- Add Java example to extract header value with default value (#639)
- Add HTTP custom method example (#954)
- Smaller fixes and additions
- Add OSGi to project in order to release each project with OSGi bundle headers (#574)
- Rename root project to ‘akka-http-root’ (#1030)
- Ignore unsupported
*/xyzmedia types (#1072)
- Exclude port when rendering X-Forwarded-For and X-Real-Ip headers (#440)
- Fix NPE when accessing static Java constant fields (#936)
- Make sure pool log messages have “PoolGateway” set as logClass for easier filtering (#1013)
- Move special non-2xx handling from RequestContextImpl to fromStatusCodeAndHeadersAndValue marshaller (#1072)
- Handle failure while parsing the URI in parameter extraction (#1043)
extractStrictEntityprovide strict entity for inner routes (#961)
- Enable javadsl to unmarshal with default
- Smaller fixes for HttpAppHttpApp
- Fix memory leak in ALPN switcher (#886)
This is the fifth maintenance release of the Akka HTTP 10.0 series. It is primarily aimed at stability aligning the internals with the upcoming Akka 2.5 release. These steps are also the groundwork to enable Play to make use of Akka HTTP and the new Akka Streams materializer in the upcoming Play 2.6.
- New docs and API for registering custom headers with JavaDSL (#761)
- Ssl-config upgraded to 0.2.2, allows disabling/changing hostname verification (#943)
- Don’t depend on Akka internal APIs, become compatible with Akka 2.5 (#877)
- Make default exception handler logging more informative (#887)
- Unmarshal.to now uses the materializer ExecutionContext if no other provided implicitly (#947)
- Prevent longer-than-needed lingering streams by fixing DelayCancellationStage (#945)
- Avoid redirect-loop when redirectToNoTrailingSlashIfPresent was used for root path (#878)
This version of Akka HTTP must be used with Akka in version at-least 2.4.17, however it is also compatible with Akka 2.5, which has just released its Release Candidate 1.
This release contains mostly bug fixes and smaller improvements. We strongly recommend updating from 10.0.3 which introduced a regression that an Akka HTTP server can leak memory over time which will lead to OOM eventually. See #851 for more information.
- Http message and header parser now also accepts LF as end of line (as recommended in the spec) (#106)
- HttpAppHttpApp now directly extends from Directives (#875)
HttpApp.startServer(host, port)for even simpler startup. (#873)
- Multiplexer infrastructure was rewritten to support plugable StreamPrioritizerStreamPrioritizer (f06ab40)
- New documentation page about how to deal with the client-side
- Lots of small cleanups and improvements
- Fix a regression introduced in 10.0.3 that might lead to memory leaking after a server connection has been closed. (#851)
- Fix the infamous “Cannot push/pull twice” bug which occurred in relation with 100-Continue requests (like any kind of uploads of POST requests done with
- Updated Akka dependency to Akka 2.4.17. (#858)
.dilatedfor tests for better stability. (#194)
- Fix MiMa to actually check compatibility against the latest released versions. (#870)
- Throughout the code base
@DoNotInheritannotations have been added to give hints about the stability of interfaces. (#727)
This release contains mostly bug fixes, a huge number of contributed documentation fixes and small improvements.
A notable new feature is the experimental HttpAppHttpApp feature (long time users may know it from spray). It allows to create an Akka HTTP server with very little boilerplate. See its documentation. Thanks a lot, @jlprat for contributing this feature and carrying through the PR with the most comments so far.
In some cases, we need to change semantics slightly to fix bugs. Some user code may still rely on the previous behavior so we are listing them here to bring attention to potential issues.
Uri.Authority.toStringnow doesn’t render leading double slashes any more (#784)
- request URIs for requests coming in for a server set up to use TLS now carry the
- Optimize frame creation for streamed WS messages (#748)
- Provide HttpApp API for Scala and Java (#156)
- Add Java-side mapRejectionResponse (#593)
- Add Composing directives java (
- Add Unmarshaller.andThen to combine two Unmarshallers (#691)
- Lots of larger and smaller improvements to Http2 support
- Allow Java bind API to specify port zero (#660)
- Fix ConnectHttp.toHostHttps when no scheme is given
- Exclude leading double slash from Uri.Authority.toString (#784)
- Basic auth fix according to rfc7617 - ‘charset’ auth-param (#716)
- Provide correct scheme in request URI for TLS connections (#658)
- Prevent “Connection closed by peer” errors during connection closure (#459)
- Fix stream marshalling, better errors, more examples (#424)
- Don’t ignore failed future for NoContent responses (#589)
- Deprecate wrongly spelled method
- Match path maps in order of longest matching key prefix (#394)
- Don’t leak Scala classes in java Unmarshaller (#604)
- Add support for Specs2 in testkit (#485)
- Fix spray-json unmarshalling of 4-byte UTF-8 characters AKA “the 😁 fix” (#691)
- Updated spray-json dependency to 1.3.3
- A huge amount of bigger and smaller contributions from the community
- Add link to sources to every documentation page to simplify contributing small fixes
- Add search thanks to algolia (#726)
Security patch to prevent denial-of-service due to memory leak in server infrastructure.