You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pekko.apache.org by fa...@apache.org on 2023/01/23 14:42:40 UTC
[incubator-pekko-http] branch main updated: update some refs to Akka in docs (#24)
This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-pekko-http.git
The following commit(s) were added to refs/heads/main by this push:
new 8f19e2d71 update some refs to Akka in docs (#24)
8f19e2d71 is described below
commit 8f19e2d7113b653647b63603d85087482588d63c
Author: PJ Fanning <pj...@users.noreply.github.com>
AuthorDate: Mon Jan 23 14:42:34 2023 +0000
update some refs to Akka in docs (#24)
---
build.sbt | 6 +-
.../main/paradox/client-side/client-transport.md | 2 +-
.../main/paradox/client-side/connection-level.md | 4 +-
docs/src/main/paradox/client-side/host-level.md | 2 +-
docs/src/main/paradox/client-side/request-level.md | 2 +-
docs/src/main/paradox/common/caching.md | 6 +-
docs/src/main/paradox/common/json-support.md | 12 +-
docs/src/main/paradox/common/timeouts.md | 4 +-
docs/src/main/paradox/common/uri-model.md | 2 +-
docs/src/main/paradox/common/xml-support.md | 6 +-
docs/src/main/paradox/compatibility-guidelines.md | 22 +-
docs/src/main/paradox/contributing.md | 4 +-
...ing-blocking-operations-in-pekko-http-routes.md | 10 +-
.../implications-of-streaming-http-entity.md | 8 +-
docs/src/main/paradox/introduction.md | 26 +-
docs/src/main/paradox/migration-guide/index.md | 12 +-
.../migration-from-old-http-javadsl.md | 69 --
.../migration-guide/migration-from-spray.md | 282 --------
.../migration-guide/migration-guide-10.0.x.md | 8 -
.../migration-guide/migration-guide-10.1.x.md | 8 -
.../migration-guide/migration-guide-10.2.x.md | 320 ---------
.../migration-guide-2.4.x-10.0.x.md | 51 --
docs/src/main/paradox/release-notes/10.0.x.md | 544 --------------
docs/src/main/paradox/release-notes/10.1.x.md | 790 ---------------------
docs/src/main/paradox/release-notes/10.2.x.md | 721 -------------------
docs/src/main/paradox/release-notes/index.md | 8 +-
.../basic-directives/extractMaterializer.md | 2 +-
.../directives/caching-directives/index.md | 6 +-
.../getFromBrowseableDirectory.md | 2 +-
.../getFromDirectory.md | 4 +-
.../file-and-resource-directives/getFromFile.md | 4 +-
.../future-directives/onCompleteWithBreaker.md | 2 +-
.../directives/method-directives/head.md | 2 +-
.../security-directives/authenticateBasic.md | 2 +-
.../security-directives/authenticateBasicAsync.md | 2 +-
.../security-directives/authenticateOAuth2.md | 4 +-
.../security-directives/authenticateOAuth2Async.md | 2 +-
.../security-directives/authenticateOAuth2PF.md | 4 +-
.../authenticateOAuth2PFAsync.md | 2 +-
.../directives/security-directives/index.md | 4 +-
.../timeout-directives/extractRequestTimeout.md | 2 +-
.../timeout-directives/withRequestTimeout.md | 4 +-
.../withRequestTimeoutResponse.md | 2 +-
.../timeout-directives/withoutRequestTimeout.md | 4 +-
.../main/paradox/routing-dsl/exception-handling.md | 2 +-
docs/src/main/paradox/routing-dsl/index.md | 4 +-
docs/src/main/paradox/routing-dsl/routes.md | 2 +-
.../routing-dsl/source-streaming-support.md | 10 +-
docs/src/main/paradox/routing-dsl/testkit.md | 12 +-
docs/src/main/paradox/security.md | 49 +-
.../2016-09-30-windows-directory-traversal.md | 62 --
docs/src/main/paradox/security/2016.md | 9 -
...ce-via-leak-on-unconsumed-closed-connections.md | 42 --
...e-in-accept-header-causes-stackoverflowerror.md | 50 --
docs/src/main/paradox/security/2017.md | 10 -
...18-09-05-denial-of-service-via-decodeRequest.md | 43 --
docs/src/main/paradox/security/2018.md | 9 -
...correct-handling-of-Transfer-Encoding-header.md | 58 --
...2021-42697-stack-overflow-parsing-user-agent.md | 53 --
docs/src/main/paradox/security/2021.md | 9 -
.../paradox/server-side/graceful-termination.md | 18 +-
docs/src/main/paradox/server-side/http2.md | 2 +-
docs/src/main/paradox/server-side/index.md | 12 +-
docs/src/main/paradox/server-side/low-level-api.md | 36 +-
.../paradox/server-side/server-https-support.md | 4 +-
.../main/paradox/server-side/websocket-support.md | 12 +-
docs/src/main/paradox/technologies.md | 2 +-
project/ValidatePullRequest.scala | 7 +-
68 files changed, 160 insertions(+), 3340 deletions(-)
diff --git a/build.sbt b/build.sbt
index 0dcdab8a4..473a83b16 100644
--- a/build.sbt
+++ b/build.sbt
@@ -436,14 +436,14 @@ lazy val docs = project("docs")
},
paradoxGroups := Map("Language" -> Seq("Scala", "Java")),
Compile / paradoxProperties ++= Map(
- "project.name" -> "Pekko HTTP",
- "canonical.base_url" -> "https://doc.akka.io/docs/akka-http/current",
+ "project.name" -> "Apache Pekko HTTP",
+ "canonical.base_url" -> "https://pekko.apache.org/docs/akka-http/current",
"akka.version" -> AkkaDependency.docs.version,
"akka.minimum.version25" -> AkkaDependency.minimumExpectedAkkaVersion,
"akka.minimum.version26" -> AkkaDependency.minimumExpectedAkka26Version,
"jackson.xml.version" -> Dependencies.jacksonXmlVersion,
"scalafix.version" -> _root_.scalafix.sbt.BuildInfo.scalafixVersion, // grab from scalafix plugin directly
- "extref.akka-docs.base_url" -> s"https://doc.akka.io/docs/akka/${AkkaDependency.docs.link}/%s",
+ "extref.pekko-docs.base_url" -> s"https://pekko.apache.org/docs/pekko/current/%s",
"javadoc.akka.http.base_url" -> {
val v = if (isSnapshot.value) "current" else version.value
s"https://doc.akka.io/japi/akka-http/$v"
diff --git a/docs/src/main/paradox/client-side/client-transport.md b/docs/src/main/paradox/client-side/client-transport.md
index 29b0728b8..271309292 100644
--- a/docs/src/main/paradox/client-side/client-transport.md
+++ b/docs/src/main/paradox/client-side/client-transport.md
@@ -109,7 +109,7 @@ Java
You can use @apidoc[ClientTransport.withCustomResolver](ClientTransport) to customize host name resolution. The given resolution function will be called for every connection attempt to resolve
a hostname / port combination (potentially asynchronously) to an `InetSocketAddress`.
-As a backend to implement the resolution function you can use Akka's [Async DNS Resolution](https://doc.akka.io/docs/akka/current/io-dns.html#dns-extension).
+As a backend to implement the resolution function you can use Apache Pekko's [Async DNS Resolution](https://doc.akka.io/docs/akka/current/io-dns.html#dns-extension).
Potential use cases:
diff --git a/docs/src/main/paradox/client-side/connection-level.md b/docs/src/main/paradox/client-side/connection-level.md
index e434fc7fe..576b1dd3a 100644
--- a/docs/src/main/paradox/client-side/connection-level.md
+++ b/docs/src/main/paradox/client-side/connection-level.md
@@ -60,9 +60,9 @@ explicitly drained by attaching it to `Sink.ignore()`.
Currently Apache Pekko HTTP doesn't implement client-side request timeout checking itself as this functionality can be regarded
as a more general purpose streaming infrastructure feature.
-It should be noted that Akka Streams provide various timeout functionality so any API that uses streams can benefit
+It should be noted that Apache Pekko Streams provide various timeout functionality so any API that uses streams can benefit
from the stream stages such as `idleTimeout`, `backpressureTimeout`, `completionTimeout`, `initialTimeout`
-and `throttle`. To learn more about these refer to their documentation in Akka Streams.
+and `throttle`. To learn more about these refer to their documentation in Apache Pekko Streams.
For more details about timeout support in Apache Pekko HTTP in general refer to @ref[Apache Pekko HTTP Timeouts](../common/timeouts.md).
diff --git a/docs/src/main/paradox/client-side/host-level.md b/docs/src/main/paradox/client-side/host-level.md
index fe1458af9..c3b495300 100644
--- a/docs/src/main/paradox/client-side/host-level.md
+++ b/docs/src/main/paradox/client-side/host-level.md
@@ -144,7 +144,7 @@ It's also possible to trigger the immediate termination of *all* connection pool
time by calling @scala[`Http().shutdownAllConnectionPools()`]@java[`Http.get(system).shutdownAllConnectionPools()`].
This call too produces a @scala[`Future[Unit]`]@java[`CompletionStage<Done>`] which is fulfilled when all pools have terminated.
-@scala[`Http().addClientPoolsToCoordinatedShutdown()`]@java[`Http.get(system).addClientPoolsToCoordinatedShutdown()`] will add the client connection pool shutdown to Apache Pekko's @extref[coordinated shutdown](akka-docs:coordinated-shutdown.html) so it will be called before the actor system disappears.
+@scala[`Http().addClientPoolsToCoordinatedShutdown()`]@java[`Http.get(system).addClientPoolsToCoordinatedShutdown()`] will add the client connection pool shutdown to Apache Pekko's @extref[coordinated shutdown](pekko-docs:coordinated-shutdown.html) so it will be called before the actor system disappears.
@@@ note
When encountering unexpected @apidoc[akka.stream.AbruptTerminationException] exceptions during @apidoc[akka.actor.ActorSystem] **shutdown**
diff --git a/docs/src/main/paradox/client-side/request-level.md b/docs/src/main/paradox/client-side/request-level.md
index e46dd47c7..51932f712 100644
--- a/docs/src/main/paradox/client-side/request-level.md
+++ b/docs/src/main/paradox/client-side/request-level.md
@@ -39,7 +39,7 @@ Java
### Using the Future-Based API in Actors
-When using the @scala[`Future`]@java[`CompletionStage`] based API from inside a classic Akka @apidoc[Actor], all the usual caveats apply to how one should deal
+When using the @scala[`Future`]@java[`CompletionStage`] based API from inside a classic Apache Pekko @apidoc[Actor], all the usual caveats apply to how one should deal
with the futures completion. For example, you should not access the actor's state from within the @scala[`Future`]@java[`CompletionStage`]'s callbacks
(such as `map`, `onComplete`, ...) and, instead, you should use the @scala[`pipeTo`]@java[`pipe`] pattern to pipe the result back
to the actor as a message:
diff --git a/docs/src/main/paradox/common/caching.md b/docs/src/main/paradox/common/caching.md
index ca4a109a4..cdb3b6876 100644
--- a/docs/src/main/paradox/common/caching.md
+++ b/docs/src/main/paradox/common/caching.md
@@ -18,12 +18,12 @@ time-based entry expiration.
To use Apache Pekko HTTP Caching, add the module to your project:
@@dependency [sbt,Gradle,Maven] {
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol="PekkoHttpVersion"
value="$project.version$"
group="org.apache.pekko"
artifact="pekko-http-caching_$scala.binary.version$"
- version="AkkaHttpVersion"
+ version="PekkoHttpVersion"
}
## Basic design
diff --git a/docs/src/main/paradox/common/json-support.md b/docs/src/main/paradox/common/json-support.md
index 8a62d3edf..ee788576d 100644
--- a/docs/src/main/paradox/common/json-support.md
+++ b/docs/src/main/paradox/common/json-support.md
@@ -12,12 +12,12 @@ See [the list of current community extensions for Apache Pekko HTTP](https://akk
To make use of the support module for (un)marshalling from and to JSON with [Jackson], add a library dependency onto:
@@dependency [sbt,Gradle,Maven] {
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol="PekkoHttpVersion"
value="$project.version$"
group="org.apache.pekko"
artifact="pekko-http-jackson_$scala.binary.version$"
- version="AkkaHttpVersion"
+ version="PekkoHttpVersion"
}
Use `akka.http.javadsl.marshallers.jackson.Jackson.unmarshaller(T.class)` to create an @apidoc[Unmarshaller[HttpEntity,T]] which expects the request
@@ -45,12 +45,12 @@ that an implicit `spray.json.RootJsonReader` and/or `spray.json.RootJsonWriter`
To enable automatic support for (un)marshalling from and to JSON with [spray-json], add a library dependency onto:
@@dependency [sbt,Gradle,Maven] {
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol="PekkoHttpVersion"
value="$project.version$"
group="org.apache.pekko"
artifact="pekko-http-spray-json_$scala.binary.version$"
- version="AkkaHttpVersion"
+ version="PekkoHttpVersion"
}
Next, provide a `RootJsonFormat[T]` for your type and bring it into scope. Check out the [spray-json] documentation for more info on how to do this.
diff --git a/docs/src/main/paradox/common/timeouts.md b/docs/src/main/paradox/common/timeouts.md
index f6f29ac52..23bd21c78 100644
--- a/docs/src/main/paradox/common/timeouts.md
+++ b/docs/src/main/paradox/common/timeouts.md
@@ -51,11 +51,11 @@ It can be configured using the `akka.http.server.bind-timeout` setting.
The linger timeout is the time period the HTTP server implementation will keep a connection open after
all data has been delivered to the network layer. This setting is similar to the SO_LINGER socket option
-but does not only include the OS-level socket but also covers the Akka IO / Akka Streams network stack.
+but does not only include the OS-level socket but also covers the Appache Pekko IO and Streams network stack.
The setting is an extra precaution that prevents clients from keeping open a connection that is
already considered completed from the server side.
-If the network level buffers (including the Akka Stream / Akka IO networking stack buffers)
+If the network level buffers (including the Appache Pekko IO and Streams networking stack buffers)
contains more data than can be transferred to the client in the given time when the server-side considers
to be finished with this connection, the client may encounter a connection reset.
diff --git a/docs/src/main/paradox/common/uri-model.md b/docs/src/main/paradox/common/uri-model.md
index 5fc1cbb1a..2ecca30c0 100644
--- a/docs/src/main/paradox/common/uri-model.md
+++ b/docs/src/main/paradox/common/uri-model.md
@@ -79,7 +79,7 @@ To extract URI components with directives, see following references:
### Obtaining the raw request URI
Sometimes it may be needed to obtain the "raw" value of an incoming URI, without applying any escaping or parsing to it.
-While this use case is rare, it comes up every once in a while. It is possible to obtain the "raw" request URI in Akka
+While this use case is rare, it comes up every once in a while. It is possible to obtain the "raw" request URI in Apache Pekko
HTTP Server side by turning on the `akka.http.server.raw-request-uri-header` flag.
When enabled, a `Raw-Request-URI` header will be added to each request. This header will hold the original raw request's
URI that was used. For an example check the reference configuration.
diff --git a/docs/src/main/paradox/common/xml-support.md b/docs/src/main/paradox/common/xml-support.md
index f88a10dd8..2e5e3197e 100644
--- a/docs/src/main/paradox/common/xml-support.md
+++ b/docs/src/main/paradox/common/xml-support.md
@@ -36,12 +36,12 @@ In order to enable support for (un)marshalling from and to XML with [Scala XML][
the following dependency:
@@dependency [sbt,Gradle,Maven] {
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol="PekkoHttpVersion"
value="$project.version$"
group="org.apache.pekko"
artifact="pekko-http-xml_$scala.binary.version$"
- version="AkkaHttpVersion"
+ version="PekkoHttpVersion"
}
Once you have done this (un)marshalling between XML and `NodeSeq` instances should work nicely and transparently,
diff --git a/docs/src/main/paradox/compatibility-guidelines.md b/docs/src/main/paradox/compatibility-guidelines.md
index ed977d96b..89a52ee1b 100644
--- a/docs/src/main/paradox/compatibility-guidelines.md
+++ b/docs/src/main/paradox/compatibility-guidelines.md
@@ -2,14 +2,14 @@
## Binary Compatibility Rules
-Apache Pekko HTTP follows the same binary compatibility rules as Akka itself.
+Apache Pekko HTTP follows the same binary compatibility rules as Apache Pekko itself.
In short it means that the versioning scheme should be read as `major.minor.patch`,
wherein all versions with the same `major` version are backwards binary-compatible,
with the exception of `@ApiMayChange`, `@InternalApi` or `@DoNotInherit` marked APIs
or other specifically documented special-cases.
For more information and a detailed discussion of these rules and guarantees please refer to
-@extref:[The @DoNotInherit and @ApiMayChange markers](akka-docs:common/binary-compatibility-rules.html#the-donotinherit-and-apimaychange-markers).
+@extref:[The @DoNotInherit and @ApiMayChange markers](pekko-docs:common/binary-compatibility-rules.html#the-donotinherit-and-apimaychange-markers).
### Components with no Binary Compatibility Guarantee
@@ -124,10 +124,10 @@ The Apache Pekko HTTP Team currently does not intend to break binary compatibili
## Specific versions inter-op discussion
-In this section we discuss some of the specific cases of compatibility between versions of Apache Pekko HTTP and Akka itself.
+In this section we discuss some of the specific cases of compatibility between versions of Apache Pekko HTTP and Apache Pekko itself.
For example, you may be interested in those examples if you encountered the following exception in your system when upgrading parts
-of your libraries: `Detected java.lang.NoSuchMethodError error, which MAY be caused by incompatible Pekko versions on the classpath. Please note that a given Pekko version MUST be the same across all modules of Pekko that you are using, e.g. if you use pekko-actor [2.5.3 (resolved from current classpath)] all other core Apache Pekko modules MUST be of the same version. External projects like Apache Pekko Connectors, Persistence plugins or Apache Pekko HTTP etc. have their own version num [...]
+of your libraries: `Detected java.lang.NoSuchMethodError error, which MAY be caused by incompatible Pekko versions on the classpath. Please note that a given Pekko version MUST be the same across all modules of Apache Pekko that you are using, e.g. if you use pekko-actor [2.5.3 (resolved from current classpath)] all other core Apache Pekko modules MUST be of the same version. External projects like Apache Pekko Connectors, Persistence plugins or Apache Pekko HTTP etc. have their own vers [...]
### Compatibility with Apache Pekko
@@ -138,15 +138,15 @@ a manual dependency to `pekko-stream`.
The same goes for `pekko-http-testkit`: If the testkit is used, explicitly declare the dependency on `pekko-stream-testkit` of same Pekko version as `pekko-stream`.
@@dependency [sbt,Gradle,Maven] {
- symbol1=AkkaVersion
+ symbol1=PekkoVersion
value1=$akka.version$
bomGroup2=org.apache.pekko
bomArtifact2=pekko-http-bom_$scala.binary.version$
- bomVersionSymbols2=AkkaHttpVersion
- symbol2="AkkaHttpVersion"
+ bomVersionSymbols2=PekkoHttpVersion
+ symbol2="PekkoHttpVersion"
value2="$project.version$"
- group1="org.apache.pekko" artifact1="pekko-http_$scala.binary.version$" version1="AkkaHttpVersion"
- group2="org.apache.pekko" artifact2="pekko-stream_$scala.binary.version$" version2=AkkaVersion
- group3="org.apache.pekko" artifact3="pekko-http-testkit_$scala.binary.version$" version3=AkkaHttpVersion scope3=Test
- group4="org.apache.pekko" artifact4="pekko-stream-testkit_$scala.binary.version$" version4=AkkaVersion scope4=Test
+ group1="org.apache.pekko" artifact1="pekko-http_$scala.binary.version$" version1="PekkoHttpVersion"
+ group2="org.apache.pekko" artifact2="pekko-stream_$scala.binary.version$" version2=PekkoVersion
+ group3="org.apache.pekko" artifact3="pekko-http-testkit_$scala.binary.version$" version3=PekkoHttpVersion scope3=Test
+ group4="org.apache.pekko" artifact4="pekko-stream-testkit_$scala.binary.version$" version4=PekkoVersion scope4=Test
}
diff --git a/docs/src/main/paradox/contributing.md b/docs/src/main/paradox/contributing.md
index eba0b93c2..ac6e587fe 100644
--- a/docs/src/main/paradox/contributing.md
+++ b/docs/src/main/paradox/contributing.md
@@ -25,8 +25,8 @@ Maven
...
<repositories>
<repository>
- <id>akka-http-snapshots</id>
- <name>Akka HTTP Snapshots</name>
+ <id>pekko-http-snapshots</id>
+ <name>Pekko HTTP Snapshots</name>
<url>https://oss.sonatype.org/content/repositories/snapshots</url>
</repository>
</repositories>
diff --git a/docs/src/main/paradox/handling-blocking-operations-in-pekko-http-routes.md b/docs/src/main/paradox/handling-blocking-operations-in-pekko-http-routes.md
index c794675e2..230e95145 100644
--- a/docs/src/main/paradox/handling-blocking-operations-in-pekko-http-routes.md
+++ b/docs/src/main/paradox/handling-blocking-operations-in-pekko-http-routes.md
@@ -23,7 +23,7 @@ Often when integrating with existing libraries or systems it is not possible to
avoid blocking APIs. The following solution explains how to handle blocking
operations properly.
-Note that the same hints apply to managing blocking operations anywhere in Akka,
+Note that the same hints apply to managing blocking operations anywhere in Apache Pekko,
including in Actors etc.
@@@
@@ -62,7 +62,7 @@ default pool which is the _global_ `ForkJoinPool.commonPool()`. With Scala Futur
provided dispatcher would be used. Both these dispatchers are ForkJoin pools by default, and are
not best suited for blocking operations.
@@@
-For example, the above screenshot shows an Akka FJP dispatchers threads,
+For example, the above screenshot shows an Apache Pekko FJP dispatchers threads,
named "`default-akka.default-dispatcher2,3,4`" going into the blocking state, after having been idle.
It can be observed that the number of new threads increases, "`default-akka.actor.default-dispatcher 18,19,20,...`"
however they go to sleep state immediately, thus wasting the resources.
@@ -93,7 +93,7 @@ my-blocking-dispatcher {
}
```
-There are many dispatcher options available which can be found in @extref[Dispatchers](akka-docs:dispatchers.html).
+There are many dispatcher options available which can be found in @extref[Dispatchers](pekko-docs:dispatchers.html).
Here `thread-pool-executor` is used, which has a hardcoded limit of threads. It keeps a set number of threads
available that allow for safe isolation of the blocking operations. The size settings should depend on the app's
@@ -131,5 +131,5 @@ This is the recommended way of dealing with any kind of blocking in reactive
applications. It is referred to as "bulkheading" or "isolating" the bad behaving
parts of an app. In this case, bad behaviour of blocking operations.
-There is good documentation available in Akka docs section,
-@extref[Blocking needs careful management](akka-docs:dispatchers.html#blocking-needs-careful-management).
+There is good documentation available in Apache Pekko docs section,
+@extref[Blocking needs careful management](pekko-docs:dispatchers.html#blocking-needs-careful-management).
diff --git a/docs/src/main/paradox/implications-of-streaming-http-entity.md b/docs/src/main/paradox/implications-of-streaming-http-entity.md
index f554fcbf6..f2504482b 100644
--- a/docs/src/main/paradox/implications-of-streaming-http-entity.md
+++ b/docs/src/main/paradox/implications-of-streaming-http-entity.md
@@ -1,6 +1,6 @@
# Implications of the streaming nature of Request/Response Entities
-Apache Pekko HTTP is streaming *all the way through*, which means that the back-pressure mechanisms enabled by Akka Streams
+Apache Pekko HTTP is streaming *all the way through*, which means that the back-pressure mechanisms enabled by Apache Pekko Streams
are exposed through all layers–from the TCP layer, through the HTTP server, all the way up to the user-facing @apidoc[HttpRequest]
and @apidoc[HttpResponse] and their @apidoc[HttpEntity] APIs.
@@ -40,7 +40,7 @@ which can be done via running the underlying `dataBytes` Source.
It is encouraged to use various streaming techniques to utilise the underlying infrastructure to its fullest,
for example by framing the incoming chunks, parsing them line-by-line and then connecting the flow into another
-destination Sink, such as a File or other Akka Streams connector:
+destination Sink, such as a File or other Apache Pekko Streams connector:
Scala
: @@snip [HttpClientExampleSpec.scala](/docs/src/test/scala/docs/http/scaladsl/HttpClientExampleSpec.scala) { #manual-entity-consume-example-1 }
@@ -58,9 +58,9 @@ Scala
Java
: @@snip [HttpClientExampleDocTest.java](/docs/src/test/java/docs/http/javadsl/HttpClientExampleDocTest.java) { #manual-entity-consume-example-2 }
-### Integrating with Akka Streams
+### Integrating with Apache Pekko Streams
-In some cases, it is necessary to process the results of a series of Apache Pekko HTTP calls as Akka Streams. In order
+In some cases, it is necessary to process the results of a series of Apache Pekko HTTP calls as Apache Pekko Streams. In order
to ensure that the HTTP Response Entity is consumed in a timely manner, the Apache Pekko HTTP stream for each request must
be executed and completely consumed, then sent along for further processing.
diff --git a/docs/src/main/paradox/introduction.md b/docs/src/main/paradox/introduction.md
index 0f1e2b78d..ab381f0e0 100644
--- a/docs/src/main/paradox/introduction.md
+++ b/docs/src/main/paradox/introduction.md
@@ -30,17 +30,17 @@ come from Play and want to try Apache Pekko HTTP, we collected a @ref[side-by-si
Apache Pekko HTTP is provided as independent modules from Apache Pekko itself under its own release cycle.
The modules, however, do *not* depend on `pekko-actor` or `pekko-stream`, so the user is required to
-choose an Pekko version to run against and add a manual dependency to `pekko-stream` of the chosen version.
+choose an Apache Pekko version to run against and add a manual dependency to `pekko-stream` of the chosen version.
@@dependency [sbt,Gradle,Maven] {
- symbol1=AkkaVersion
+ symbol1=PekkoVersion
value1=$akka.version$
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol2="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol2="PekkoHttpVersion"
value2="$project.version$"
- group1="org.apache.pekko" artifact1="pekko-actor-typed_$scala.binary.version$" version1=AkkaVersion
- group2="org.apache.pekko" artifact2="pekko-stream_$scala.binary.version$" version2=AkkaVersion
- group3="org.apache.pekko" artifact3="pekko-http_$scala.binary.version$" version3="AkkaHttpVersion"
+ group1="org.apache.pekko" artifact1="pekko-actor-typed_$scala.binary.version$" version1=PekkoVersion
+ group2="org.apache.pekko" artifact2="pekko-stream_$scala.binary.version$" version2=PekkoVersion
+ group3="org.apache.pekko" artifact3="pekko-http_$scala.binary.version$" version3="PekkoHttpVersion"
}
You may download a packaged version of this project by clicking "Create a project for me!" on the
@@ -104,12 +104,12 @@ for JSON. An additional module provides JSON serialization using the spray-json
for details):
@@dependency [sbt,Gradle,Maven] {
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol="PekkoHttpVersion"
value="$project.version$"
group="org.apache.pekko"
artifact="pekko-http-spray-json_$scala.binary.version$"
- version="AkkaHttpVersion"
+ version="PekkoHttpVersion"
}
@@@
@@ -118,12 +118,12 @@ JSON support is possible in `pekko-http` by the use of Jackson, an external arti
for details):
@@dependency [sbt,Gradle,Maven] {
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol="PekkoHttpVersion"
value="$project.version$"
group="org.apache.pekko"
artifact="pekko-http-jackson_$scala.binary.version$"
- version="AkkaHttpVersion"
+ version="PekkoHttpVersion"
}
@@@
diff --git a/docs/src/main/paradox/migration-guide/index.md b/docs/src/main/paradox/migration-guide/index.md
index a3fc5b10e..658d7ed8e 100644
--- a/docs/src/main/paradox/migration-guide/index.md
+++ b/docs/src/main/paradox/migration-guide/index.md
@@ -2,13 +2,5 @@
@@toc { depth=3 }
-@@@ index
-
-* [migration-guide-10.2.x](migration-guide-10.2.x.md)
-* [migration-guide-10.1.x](migration-guide-10.1.x.md)
-* [migration-guide-10.0.x](migration-guide-10.0.x.md)
-* [migration-guide-2.4.x-10.0.x](migration-guide-2.4.x-10.0.x.md)
-* [migration-from-spray](migration-from-spray.md)
-* [migration-from-old-http-javadsl](migration-from-old-http-javadsl.md)
-
-@@@
+* If you are currently using an old version of Akka HTTP or Spray, you should first follow the [Akka HTTP migration guide](https://doc.akka.io/docs/akka-http/10.2/migration-guide/index.html)
+* We will soon provide a guide for migrating from Akka HTTP v10.2 to Apache Pekko HTTP
diff --git a/docs/src/main/paradox/migration-guide/migration-from-old-http-javadsl.md b/docs/src/main/paradox/migration-guide/migration-from-old-http-javadsl.md
deleted file mode 100644
index fc4957d35..000000000
--- a/docs/src/main/paradox/migration-guide/migration-from-old-http-javadsl.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Migration Guide from "old" HTTP JavaDSL
-
-The so-called "old" JavaDSL for Akka HTTP was initially developed during the project's experimental phase,
-and thanks to multiple user comments and contributions we were able to come up with a more Java 8 "feel",
-which at the same time is also closer to the existing ScalaDSL.
-
-The previous DSL has been entirely removed and replaced with the the so-called "new" one.
-Upgrading to the new DSL is **highly encouraged** since the old one not only was rather hard to work with,
-it actually was not possible to express many typical use-cases using it.
-
-The most major changes include:
-
-## HttpApp is gone
-
-We removed @apidoc[HttpApp], which was a helper class containing a `main()` implementation, as we would like to encourage understanding
-how the various elements of the API fit together.
-
-Instead developers should start applications "manually", by converting a @scala[@scaladoc[Route](akka.http.scaladsl.server.index#Route=akka.http.scaladsl.server.RequestContext=%3Escala.concurrent.Future[akka.http.scaladsl.server.RouteResult])]@java[@javadoc[Route](akka.http.javadsl.server.Route)] to a @apidoc[Flow[HttpRequest, HttpResponse, ?]]
-using the `Route.flow` method. For examples of full apps refer to @ref[Route Testkit](../routing-dsl/testkit.md).
-
-## `RequestVal` is gone
-
-The old API heavily relied on the concept of "request values" which could be used to extract a value from a request context.
-
-Based on community feedback and our own experience we found them too hard to work with in more complex settings.
-The concept of a request value has been completely removed, and replaced with proper "directives", exactly like in the ScalaDSL.
-
-**Previously**:
-
-```java
-RequestVal<Host> host = Headers.byClass(Host.class).instance();
-
-final Route route =
- route(
- handleWith1(host, (ctx, h) ->
- ctx.complete(String.format("Host header was: %s", h.host()))
- )
- );
-```
-
-**Now**:
-
-```java
-final Route route =
- headerValueByType(Host.class, host -> complete("Host was: " + host));
-```
-
-## All of ScalaDSL routing has corresponding JavaDSL
-
-Both @scala[@scaladoc[Route](akka.http.scaladsl.server.index#Route=akka.http.scaladsl.server.RequestContext=%3Escala.concurrent.Future[akka.http.scaladsl.server.RouteResult])]@java[@javadoc[Route](akka.http.javadsl.server.Route)], @apidoc[RouteResult] and other important core concepts such as `Rejections` are now modeled 1:1 with Scala,
-making is much simpler to understand one API based on the other one – tremendously useful when learning about some nice
-pattern from blogs which used Scala, yet need to apply it in Java and the other way around.
-
-It is now possible to implement marshallers using Java. Refer to @ref[Marshalling](../common/marshalling.md) & @ref[Unmarshalling](../common/unmarshalling.md) for details.
-
-## Some complete* overloads changed to completeOK*
-
-In JavaDSL when complete is called with only an entity, the `OK` response code is *assumed*,
-to make this more explicit these methods contain the word `OK` in them.
-
-This has been made more consistent than previously, across all overloads and Future-versions of these APIs.
-
-## Migration help
-
-As always, feel free to reach out via the [akka-user](https://groups.google.com/forum/#!searchin/akka-user/) mailing list or gitter channels,
-to seek help or guidance when migrating from the old APIs.
-
-For Lightbend subscription owners it is possible to reach out to the core team for help in the migration by asking specific
-questions via the [Lightbend customer portal](https://portal.lightbend.com/account/login).
diff --git a/docs/src/main/paradox/migration-guide/migration-from-spray.md b/docs/src/main/paradox/migration-guide/migration-from-spray.md
deleted file mode 100644
index 471f04fa5..000000000
--- a/docs/src/main/paradox/migration-guide/migration-from-spray.md
+++ /dev/null
@@ -1,282 +0,0 @@
-# Migration Guide from Spray
-
-Apache Pekko HTTP is the successor for spray. With the first non-experimental release of Apache Pekko HTTP, spray has reached its
-end-of-life. Apache Pekko HTTP is a reimplementation of HTTP based on pekko-stream (former spray-can) which adds streaming
-support on all levels. The popular high-level routing DSL (former spray-routing) has mostly been kept but was made
-more consistent and simplified where possible. While underlyings have changed a lot, many of the high-level
-features and syntax of the routing DSL have only changed superficially so that code can hopefully be converted with
-little effort.
-
-## Major changes
-
-### Streams everywhere
-
-Apache Pekko HTTP offers an API based on streams where spray offered an API based on actor messaging. This has important consequences.
-
-Streaming support is needed to handle request and response entities (or bodies) in a streaming fashion, i.e. being
-able to access the incoming bytes while they come in from the network without having to buffer a potentially big request
-or response in memory. The same is valid for sending out request or response data entities. In the model, the streaming
-underlyings can be seen in the @apidoc[HttpEntity] type which now has subclasses that allow to specify a @apidoc[Source[ByteString, \_]]
-to provide or consume entity data.
-
-In spray, you could configure spray-can to send out `HttpRequestPart` and `HttpResponsePart` messages to receive a request
-or a response in a streaming fashion. The default case was for spray to collect the full entity in memory and send it out
-as a @apidoc[akka.util.ByteString] as part of the request or response entity object.
-
-In Apache Pekko HTTP, handling streaming data is mandatory. When you receive a @apidoc[HttpRequest] on the server-side or an @apidoc[HttpResponse],
-in the default case it will contain a streamed entity as the `entity` field *which you are required to consume*.
-Otherwise, a connection might be stuck (at least until timeouts kick in).
-See @ref[Implications of the streaming nature of Request/Response Entities](../implications-of-streaming-http-entity.md).
-
-In the implementation, Apache Pekko HTTP makes heavy use of streams as well with the occasional fallback to actors.
-
-### New module structure
-
-The number of modules has been reduced. Here's an approximate mapping from spray modules to new modules:
-
- * spray-util, spray-http, spray-can => pekko-http-core
- * spray-routing => pekko-http
- * spray-client => parts of high-level client support is now provided via `Http().singleRequest`, other is not yet
- implemented (see also [#113](https://github.com/akka/akka-http/issues/113))
- * spray-caching => pekko-http-caching (since version 10.0.11, more information here: @ref[Documentation](../common/caching.md))
-
-### Package name changes
-
-Classes can now be found in new packages:
-
- * the model can be found in `akka.http.scaladsl.model`
- * headers can be found in `akka.http.scaladsl.model.headers._`
- * the routing DSL can be found in `akka.http.scaladsl.server._`
-
-### Routing DSL not based on shapeless any more
-
-To simplify using Pekko HTTP together with other libraries that require shapeless, the routing DSL in Apache Pekko HTTP does
-not depend on shapeless any more. Instead, we support a light-weight replacement that models heterogeneous lists with
-tuples. This will not affect you as long as you haven't written any generic directives. The implicit magic in the
-background that powers directives will - in user code - work as before.
-
-Internally, the type aliases for `DirectiveX` have changed:
-
-| | spray | Pekko HTTP |
-|----------------------|-------------------------------|-----------------------------|
-| `Directive0` | `Directive[HNil]` | `Directive[Tuple0]` |
-| `Directive1[T]` | `Directive[T :: HNil]` | `Directive[Tuple1[T]]` |
-| `Directive2[T1, T2]` | `Directive[T1 :: T2 :: HNil]` | `Directive[Tuple2[T1, T2]]` |
-
-### Support for Java
-
-All APIs are also available for Java. See everything under the `akka.http.javadsl` package.
-
-## Other changes
-
-
-### Changes in Route type
-
-Route type has changed from `Route = RequestContext => Unit` to `Route = RequestContext => Future[RouteResult]`.
-Which means that now we must complete the Request inside the controller and we can't simply pass the request to another Actor and complete it there. This has been done intentionally, because in Spray it was easy to forget to `complete` requests but the code would still compile.
-
-The following article mentions a few ways for us to complete the request based on processing outside the controller:
-[CodeMonkey blog - Actor per Request with Apache Pekko HTTP](https://markatta.com/codemonkey/blog/2016/08/03/actor-per-request-with-akka-http/)
-
-This article was written by Johan Andrén, a member of the Lightbend team.
-
-### Changes in Marshalling
-
-Marshaller.of can be replaced with `Marshaller.withFixedContentType`.
-
-Was:
-
-```scala
-Marshaller.of[JsonApiObject](`application/json`) { (value, contentType, ctx) =>
- ctx.marshalTo(HttpEntity(contentType, value.toJson.toString))
-}
-```
-
-Replace with:
-
-```scala
-Marshaller.withFixedContentType(`application/json`) { obj =>
- HttpEntity(`application/json`, obj.toJson.compactPrint)
-}
-```
-
-Apache Pekko HTTP marshallers support content negotiation, now it's not necessary to specify content type
-when creating one “super” marshaller from other marshallers:
-
-Before:
-
-```scala
-ToResponseMarshaller.oneOf(
- `application/vnd.api+json`,
- `application/json`
-)(
- jsonApiMarshaller,
- jsonMarshaller
-}
-```
-
-After:
-
-```scala
-Marshaller.oneOf(
- jsonApiMarshaller,
- jsonMarshaller
-)
-```
-
-### Changes in Unmarshalling
-
-Apache Pekko HTTP contains a set of predefined unmarshallers. This means that scala code like this:
-
-```scala
-Unmarshaller[Entity](`application/json`) {
- case HttpEntity.NonEmpty(contentType, data) =>
- data.asString.parseJson.convertTo[Entity]
-}
-```
-
-needs to be changed into:
-
-```scala
-Unmarshaller
- .stringUnmarshaller
- .forContentTypes(`application/json`)
- .map(_.parseJson.convertTo[Entity])
-```
-
-### Changes in MediaTypes
-
-`MediaType.custom` can be replaced with specific methods in @apidoc[MediaType] object.
-
-Was:
-
-```scala
-MediaType.custom("application/vnd.acme+json")
-```
-
-Replace with:
-
-```scala
-MediaType.applicationWithFixedCharset("vnd.acme+json", HttpCharsets.`UTF-8`)
-```
-
-### Changes in Rejection Handling
-
-`RejectionHandler` now uses a builder pattern – see the example:
-
-Before:
-
-```scala
-def rootRejectionHandler = RejectionHandler {
- case Nil =>
- requestUri { uri =>
- logger.error("Route: {} does not exist.", uri)
- complete((NotFound, mapErrorToRootObject(notFoundError)))
- }
- case AuthenticationFailedRejection(cause, challengeHeaders) :: _ => {
- logger.error(s"Request is rejected with cause: $cause")
- complete((Unauthorized, mapErrorToRootObject(unauthenticatedError)))
- }
-}
-```
-
-After:
-
-```scala
-RejectionHandler
-.newBuilder()
-.handle {
- case AuthenticationFailedRejection(cause, challengeHeaders) =>
- logger.error(s"Request is rejected with cause: $cause")
- complete(Unauthorized, mapErrorToRootObject(unauthenticatedError))
-.handleNotFound { ctx =>
- logger.error("Route: {} does not exist.", ctx.request.uri.toString())
- ctx.complete(NotFound, mapErrorToRootObject(notFoundError))
-}
-.result()
-.withFallback(RejectionHandler.default)
-```
-
-### Changes in HTTP Client
-
-The Spray-client pipeline was removed. Http’s `singleRequest` should be used instead of `sendReceive`:
-
-```scala
-//this will not longer work
-val token = Authorization(OAuth2BearerToken(accessToken))
-val pipeline: HttpRequest => Future[HttpResponse] = (addHeader(token) ~> sendReceive)
-val patch: HttpRequest = Patch(uri, object))
-
-pipeline(patch).map { response =>
- …
-}
-```
-
-needs to be changed into:
-
-```scala
-val request = HttpRequest(
- method = PATCH,
- uri = Uri(uri),
- headers = List(Authorization(OAuth2BearerToken(accessToken))),
- entity = HttpEntity(MediaTypes.`application/json`, object)
-)
-
-http.singleRequest(request).map {
- case … => …
-}
-```
-
-### Changes in form fields and file upload directives
-
-With the streaming nature of http entity, it’s important to have a strict http entity before accessing
-multiple form fields or use file upload directives.
-One solution might be using next directive before working with form fields:
-
-```scala
-val toStrict: Directive0 = extractRequest flatMap { request =>
- onComplete(request.entity.toStrict(5.seconds)) flatMap {
- case Success(strict) =>
- mapRequest( req => req.copy(entity = strict))
- case _ => reject
- }
-}
-```
-
-And one can use it like this:
-
-```scala
-toStrict {
- formFields("name".as[String]) { name =>
- ...
- }
-}
-```
-
-
-## Removed features
-
-### Removed HttpService
-
-Spray’s `HttpService` was removed. This means that scala code like this:
-
-```scala
-val service = system.actorOf(Props(new HttpServiceActor(routes)))
-IO(Http)(system) ! Http.Bind(service, "0.0.0.0", port = 8080)
-```
-
-needs to be changed into:
-
-```scala
-Http().newServerAt("0.0.0.0", port = 8080).bind(routes)
-```
-
-### Other removed features
-
- * `respondWithStatus` also known as `overrideStatusCode` has not been forward ported to Apache Pekko HTTP,
-as it has been seen mostly as an anti-pattern. More information here: <https://github.com/akka/akka/issues/18626>
- * `respondWithMediaType` was considered an anti-pattern in spray and is not ported to Apache Pekko HTTP.
-Instead users should rely on content type negotiation as Apache Pekko HTTP implements it.
-More information here: [#190](https://github.com/akka/akka-http/issues/190)
- * @ref[Registering Custom Media Types](../common/http-model.md#registeringcustommediatypes) changed from Spray in order not to rely on global state.
- * HTTP Client proxy support, see [#115 Client proxy support for HTTP](https://github.com/akka/akka-http/issues/115) and [#192 Client proxy support for HTTPS](https://github.com/akka/akka-http/issues/192) tickets for details.
diff --git a/docs/src/main/paradox/migration-guide/migration-guide-10.0.x.md b/docs/src/main/paradox/migration-guide/migration-guide-10.0.x.md
deleted file mode 100644
index 651b75950..000000000
--- a/docs/src/main/paradox/migration-guide/migration-guide-10.0.x.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Migration Guide within Akka HTTP 10.0.x
-
-## General Notes
-
-See the general @ref[compatibility guidelines](../compatibility-guidelines.md).
-
-You should first [migrate to Akka HTTP 10.2.x](https://doc.akka.io/docs/akka-http/current/migration-guide/migration-guide-10.0.x.html)
-and then migrate to Apache Pekko HTTP (TODO).
\ No newline at end of file
diff --git a/docs/src/main/paradox/migration-guide/migration-guide-10.1.x.md b/docs/src/main/paradox/migration-guide/migration-guide-10.1.x.md
deleted file mode 100644
index 9ab040bee..000000000
--- a/docs/src/main/paradox/migration-guide/migration-guide-10.1.x.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Migration Guide to and within Akka HTTP 10.1.x
-
-## General Notes
-
-See the general @ref[compatibility guidelines](../compatibility-guidelines.md).
-
-You should first [migrate to Akka HTTP 10.2.x](https://doc.akka.io/docs/akka-http/current/migration-guide/migration-guide-10.1.x.html)
-and then migrate to Apache Pekko HTTP (TODO).
\ No newline at end of file
diff --git a/docs/src/main/paradox/migration-guide/migration-guide-10.2.x.md b/docs/src/main/paradox/migration-guide/migration-guide-10.2.x.md
deleted file mode 100644
index 26472448e..000000000
--- a/docs/src/main/paradox/migration-guide/migration-guide-10.2.x.md
+++ /dev/null
@@ -1,320 +0,0 @@
-# Migration Guide to and within Akka HTTP 10.2.x
-
-## General Notes
-
-See the general @ref[compatibility guidelines](../compatibility-guidelines.md).
-
-Under these guidelines, minor version updates are supposed to be binary compatible and drop-in replacements
-for former versions under the condition that user code only uses public, stable, non-deprecated API. Especially
-libraries should make sure not to depend on deprecated API to be compatible with both 10.1.x and 10.2.x.
-
-If you find an unexpected incompatibility please let us know, so we can check whether the incompatibility is accidental,
-so we might still be able to fix it.
-
-## Akka HTTP 10.1.x -> 10.2.0
-
-10.2.0 will introduce deprecation warnings to every server project because the existing `Http.bind*` methods have been deprecated and
-replaced by the [new ServerBuild API](#new-serverbuilder-api-to-create-server-bindings). To ease the migration pain, we have prepared
-scalafix rules to automatically rewrite existing code to the new API.
-
-To run those rules, first add scalafix to your `project/plugins.sbt`:
-
-@@@vars
-
-```scala
-addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "$scalafix.version$")
-```
-
-@@@
-
-The in the sbt shell of your project run:
-
-```
-scalafixEnable
-set scalacOptions in ThisBuild += "-P:semanticdb:synthetics:on"
-scalafixAll dependency:MigrateToServerBuilder@com.typesafe.akka:akka-http-scalafix-rules:10.2.0
-```
-
-See also scalafix's [Installation](https://scalacenter.github.io/scalafix/docs/users/installation.html) and [External Rules](https://scalacenter.github.io/scalafix/docs/rules/external-rules.html)
-documentation.
-
-If your open-source project uses [scala-steward](https://github.com/scala-steward-org/scala-steward) it might already automatically
-run those scalafix migrations and include the changes in its update PR to your repository.
-
-### Hiding Materializer
-
-Recent Akka versions introduced a singleton system materializer that can be summoned from an ActorSystem automatically. In many cases,
-`Materializer` arguments are now optional and APIs have been simplified to require materializers in fewer places. In fact, most common
-uses do not require a materializer any more at all.
-
-### New ServerBuilder API to create server bindings
-
-To simplify binding servers (and to make it more consistent between Java and Scala), a new @apidoc[ServerBuilder] API has been introduced.
-The most common change needed to bind a server to handle routes will be from:
-
-Scala
-: @@snip [AkkaHttp1020MigrationSpec.scala](/docs/src/test/scala/docs/http/scaladsl/server/AkkaHttp1020MigrationSpec.scala) { #old-binding }
-
-Java
-: @@snip [AkkaHttp1020MigrationExample.java](/docs/src/test/java/docs/http/javadsl/server/AkkaHttp1020MigrationExample.java) { #old-binding }
-
-to:
-
-Scala
-: @@snip [AkkaHttp1020MigrationSpec.scala](/docs/src/test/scala/docs/http/scaladsl/server/AkkaHttp1020MigrationSpec.scala) { #new-binding }
-
-Java
-: @@snip [AkkaHttp1020MigrationExample.java](/docs/src/test/java/docs/http/javadsl/server/AkkaHttp1020MigrationExample.java) { #new-binding }
-
-
-### Scala 2.11 support dropped
-
-Almost three years after the release of Scala 2.11.12, support for Scala 2.11 has been dropped following the example of Akka 2.6.
-Akka HTTP 10.1.x which still supports Scala 2.11 will be supported for a while.
-
-### HttpRequest.copy / HttpResponse.copy deprecated in favor of withXYZ methods
-
-HttpRequest and HttpResponse have been converted from case classes to regular classes already a while ago. This was necessary to keep
-being able to make binary compatible changes to the API. So far, we kept the `copy` methods available but, like all methods with default
-parameters, these started to become a liability as well. In 10.2.0, the `copy` methods are now deprecated in favor of the more
-explicit `withXYZ` methods. This will help us to evolve those APIs in the future (as unfortunate it is that the idiomatic Scala way
-of case classes / default arguments is not an option because of our compatibility constraints).
-
-### HTTP/2 support requires JDK 8 update 252 or later
-
-JVM support for ALPN has been backported to JDK 8u252 which is now widely available. Support for using the Jetty ALPN
-agent has been dropped in 10.2.0. HTTP/2 support therefore now requires to be run on JVM >= 8u252.
-
-### Scalatest dependency upgraded to 3.1.0
-
-The Scalatest dependency for akka-http-testkit was upgraded to version 3.1.0. This version is incompatible with previous
-versions. This is relevant for user code if it uses methods from @scaladoc[ScalatestUtils](akka.http.scaladsl.testkit.ScalatestUtils)
-(which are in scope if your test extends from @scaladoc[ScalaTestRouteTest](akka.http.scaladsl.testkit.ScalaTestRouteTest)).
-In this case, the project itself needs to be updated to use Scalatest >= 3.1.0.
-
-### Providing route settings, exception and rejection handling
-
-Previously, the implicit conversion `route2HandlerFlow` that turns a `Route` into a
-`Flow[HttpRequest, HttpResponse]` allowed implicitly passing in Routing settings,
-Parser settings, custom `Materializer`, `RoutingLog` or `ExecutionContext`, and
-the `RejectionHandler`/`ExceptionHandler` to use.
-
-This has been simplified to use system defaults by default and to require explicit code if you want to change those defaults:
-
-* To set Routing or Parser settings, set them in your actor system configuration, e.g. via `application.conf`. In the rare case where you'd like to
- test routes with different @apidoc[RoutingSettings] within the same test, you can use the
- @ref[withSettings](../routing-dsl/directives/basic-directives/withSettings.md) directive.
-* To apply a custom @apidoc[http.*.RejectionHandler] or @apidoc[ExceptionHandler], use the @ref[handleRejections](../routing-dsl/directives/execution-directives/handleRejections.md)
- and @ref[handleExceptions](../routing-dsl/directives/execution-directives/handleExceptions.md) directives
-
-#### In RouteTest (scaladsl)
-
-Similarly, @apidoc[RouteTest] no longer automatically picks up such implicit values, and you
-can use the same approach to explicitly set them instead.
-
-### Strict query strings
-
-In 10.1.x, while parsing the query string of a URI, characters were accepted that are
-not allowed according to RFC 3986, even when `parsing.uri-parsing-mode` was
-set to the default value of `strict`. Parsing such URIs will now fail in `strict` mode.
-If you want to allow such characters in incoming URIs, set `parsing.uri-parsing-mode` to `relaxed`, in which case these characters will be percent-encoded automatically.
-
-### Transparent HEAD requests now disabled by default
-
-Prior to 10.2.0, when a client would perform a `HEAD` request, by default Akka HTTP would call the `GET` route but discard the body.
-This can save bandwidth in some cases, but is also counter-intuitive when you actually want to explicitly handle `HEAD` requests,
- and may increase resource usage in cases where the logic behind the `GET` request is heavy. For this reason we have changed
- the default value of `akka.http.server.transparent-head-requests` to `off`, making this feature opt-in.
-
-### Server-side HTTP pipelining now disabled by default
-
-HTTP pipelining is now disabled by default. It is not used commonly by clients because it suffers from
-head-of-line blocking. It is recommended to use pooled connections or HTTP/2 instead.
-
-HTTP pipelining is still supported and can be re-enabled by setting `pipelining-limit = n` with a value of `n > 1`.
-
-### X-Real-Ip now takes precedence over Remote-Address in extractClientIP
-
-The @ref[extractClientIP](../routing-dsl/directives/misc-directives/extractClientIP.md) now returns the value of the
-`X-Real-Ip` header when both an`X-Real-Ip` and a `Remote-Address` header is available. This directive provides a
-'best guess' of the client IP, but in a way that allows any client to provide this address in the header. For this reason
-you should never trust this value for security purposes.
-
-When you need a secure way to get the client IP, use the @apidoc[AttributeKeys.remoteAddress](AttributeKeys$) @ref[attribute](../common/http-model.md#attributes),
-or use the specific headers which are known to be set correctly by the infrastructure you do trust.
-
-### max-content-length
-
-The `max-content-length` setting can no longer be set on `akka.http.parsing`, and instead
-must now be set explicitly on `akka.http.client.parsing` and/or `akka.http.server.parsing`.
-The default for `akka.http.client.parsing.max-content-length` has been changed from `8m`
-to `infinite`.
-
-### Removal of legacy host connection pool
-
-The legacy host connection pool is the original client pool implementation from the beginnings of Akka HTTP backing
-`Http().singleRequest` and other client APIs. During the 10.0.x development the pool was reimplemented and could be
-used in an opt-in fashion. Since 10.1.0, this new pool implementation has been the default. With 10.2.0 we took the
-opportunity to remove the old pool implementation. The setting `akka.http.host-connection-pool.pool-implementation`
-has been removed as well as its code representation in `ConnectionPoolSettings`.
-
-### headerValueByType (scaladsl)
-
-When using the Scala DSL, invoking
-@ref[headerValueByType](../routing-dsl/directives/header-directives/headerValueByType.md)
-and @ref[optionalHeaderValueByType](../routing-dsl/directives/header-directives/optionalHeaderValueByType.md) by just its generic parameter, like `headerValueByType[Origin]()`, uses a Scala feature called 'argument adaptation' that is planned to
-[go away](https://github.com/scala/scala/pull/3260) in a future value of Scala.
-While you could earlier work around this by writing `headerValueByType[Origin](())`,
-we have now deprecated this as well and you are encouraged to use the companion object instead: `headerValueByType(Origin)`.
-For headers that do not have a companion object, you can `headerValueByType(classOf[UpgradeToWebSocket])`.
-
-### parameters / formFields (scaladsl)
-
-The @ref[parameters](../routing-dsl/directives/parameter-directives/parameter.md) and the
-@ref[formFields](../routing-dsl/directives/form-field-directives/formFields.md) directives
-used to rely on the 'magnet pattern'. Unfortunately, for the case where you would match
-multiple parameters, the pattern relied on a Scala feature called 'argument adaptation'
-which is planned to [go away](https://github.com/scala/scala/pull/3260) in a future version of Scala.
-
-Earlier, you would have to work around this by including double parentheses, like this (same for `formFields`):
-
- parameters(("a".as[Int], "b".as[Int]))
-
-We have changed the implementation of the directives in a way that is binary compatible
-and source compatible, with one exception: previously, `<name>.requiredValue` would match and check
-a parameter, but it would not be extracted by the directive. From 10.2.0 forward it will
-be extracted by the directive even when it is required.
-
-This means when in the past you had:
-
- parameter("nose".requiredValue("large")) { complete("Ok!") }
-
-You would now have
-
- parameter("nose".requiredValue("large")) { _ => complete("Ok!") }
-
-This is especially relevant when you were combining parameters directives with other
-directives using `|`: since the output types of the directives on both 'sides' of the `|` need to be equal, where you previously might have had:
-
- (post | parameter("method".requiredValue("post"))) { complete("POST") }
-
-You will now have to explicitly discard the parameter value:
-
- (post | parameter("method".requiredValue("post")).tmap(_ => ())) { complete("POST") }
-
-
-### Coding infrastructure is now internal
-
-Previously, the coding infrastructure has been mostly public, exposing API that was never intended to be public.
-Most of the existing classes have now been marked as internal and deprecated. This will allow us to remove the
-coding infrastructure from akka-http itself in the future and use implementations provided by akka-stream directly.
-
-Only parts of `Encoder`, `Decoder`, and `Coder` are still public. Predefined coders that have been available as
-e.g. `akka.http.scaladsl.coding.Gzip` are now available as `scaladsl.coding.Coders.Gzip`, `Coders.Deflate`, and
-`Coders.NoCoding`. Coding directives that use the default coding setup, like `encodeResponse` and `decodeRequest`
-continue to work without changes necessary.
-
-### Configuring HTTPS connections
-
-Akka HTTP no longer uses the HTTPS configuration configured with `ssl-config`
-by default. Instead, it will use the JRE defaults for client connections. For
-server connections you should create a @apidoc[HttpsConnectionContext] with
-the relevant configuration.
-
-Previously, the SSL configuration was constructed based on the parameters
-you pass to @apidoc[HttpsConnectionContext$] and the logic and configuration
-used by the [ssl-config](https://lightbend.github.io/ssl-config/) library. This was
-because back then the default JDK SSL configuration was a bad match for HTTP
-connections. Nowadays, however, the JDK defaults are much better and the
-use of `ssl-config` makes the configuration hard to reason about.
-
-For this reason, we have deprecated the `ssl-config`-based APIs, and now
-provide @apidoc[ConnectionContext.httpsServer](ConnectionContext$)
-and @apidoc[ConnectionContext.httpsClient](ConnectionContext$)
-that will use the JDK defaults. There is also a
-@apidoc[ConnectionContext.https](ConnectionContext$)
-where you can provide your own logic for creating `SSLEngine` instances.
-When using this more low-level API, remember it is up to you to set the
-`SSLEngine` 'mode' (client or server), and further configuration such as
-enabling SNI and hostname verification features when needed.
-
-### List of deprecated and deleted APIs
-
-#### Deprecated APIs
-
-javadsl:
-
- * static `akka.http.javadsl.ConnectionContext.https`
- * most getters of `akka.http.javadsl.ConnectionContext`
- * `akka.http.javadsl.Http.bind`
- * `akka.http.javadsl.Http.bindAndHandle`
- * `akka.http.javadsl.Http.bindAndHandleSync`
- * `akka.http.javadsl.Http.bindAndHandleAsync`
- * `akka.http.javadsl.Http.defaultServerHttpContext`
- * `akka.http.javadsl.Http.setDefaultServerHttpContext`
- * `akka.http.javadsl.Http.createServerHttpsContext`
- * `akka.http.javadsl.Http.createClientHttpsContext`
- * `akka.http.javadsl.Http.createDefaultClientHttpsContext`
- * `akka.http.javadsl.model.ws.UpgradeToWebSocket`
- * `akka.http.javadsl.server.HttpApp`
- * `akka.http.javadsl.settings.ParserSettings.create`
- * `akka.http.javadsl.settings.ServerSettings.getRemoteAddressHeader`
- * `akka.http.javadsl.settings.ServerSettings.getWebsocketRandomFactory`
- * `akka.http.javadsl.settings.ServerSettings.withWebsocketRandomFactory`
- * `akka.http.javadsl.server.directives.WebSocketDirectives.extractUpgradeToWebSocket`
-
-scaladsl:
-
- * most of `akka.http.scaladsl.ConnectionContext`
- * `akka.http.scaladsl.HttpExt.bind`
- * `akka.http.scaladsl.HttpExt.bindAndHandle`
- * `akka.http.scaladsl.HttpExt.bindAndHandleSync`
- * `akka.http.scaladsl.HttpExt.bindAndHandleAsync`
- * `akka.http.scaladsl.Http.defaultServerHttpContext`
- * `akka.http.scaladsl.Http.setDefaultServerHttpContext`
- * `akka.http.scaladsl.Http.createClientHttpsContext`
- * `akka.http.scaladsl.Http.createDefaultClientHttpsContext`
- * `akka.http.scaladsl.model.HttpCookie.copy`
- * `akka.http.scaladsl.model.HttpCookie.unapply`
- * `akka.http.scaladsl.model.HttpRequest.copy`
- * `akka.http.scaladsl.model.HttpResponse.copy`
- * `akka.http.scaladsl.model.headers.Remote-Address`
- * `akka.http.scaladsl.model.ws.UpgradeToWebSocket`
- * `akka.http.scaladsl.server.HttpApp`
- * `akka.http.scaladsl.settings.ParserSettings.apply`
- * `akka.http.scaladsl.settings.ServerSettings.remoteAddressHeader`
- * `akka.http.scaladsl.settings.ServerSettings.getWebsocketRandomFactory`
- * `akka.http.scaladsl.settings.ServerSettings.withWebsocketRandomFactory`
- * `akka.http.scaladsl.coding.Deflate`
- * `akka.http.scaladsl.coding.DeflateCompressor`
- * `akka.http.scaladsl.coding.StreamDecoder`
- * `akka.http.scaladsl.coding.Encoder.encode(ByteString): ByteString`
- * `akka.http.scaladsl.coding.Encoder.newCompressor`
- * `akka.http.scaladsl.coding.Encoder.newEncodeTransformer`
- * `akka.http.scaladsl.coding.Compressor`
- * `akka.http.scaladsl.coding.Gzip`
- * `akka.http.scaladsl.coding.NoCoding`
- * `akka.http.scaladsl.server.Route.asyncHandler`
- * `akka.http.scaladsl.server.directives.FormFieldDirectives.FieldMagnet`
- * `akka.http.scaladsl.server.directives.FormFieldDirectives.FieldDef`
- * `akka.http.scaladsl.server.directives.FormFieldDirectives.FieldDefAux`
- * `akka.http.scaladsl.server.directives.HeaderDirectives.headerValueByName`
- * `akka.http.scaladsl.server.directives.HeaderDirectives.optionalHeaderValueByName`
- * `akka.http.scaladsl.server.directives.HeaderDirectives.fromUnitForModeledCustomHeader`
- * `akka.http.scaladsl.server.directives.HeaderDirectives.fromUnitNormalHeader`
- * `akka.http.scaladsl.server.directives.WebSocketDirectives.extractUpgradeToWebSocket`
-
-#### Deleted APIs (or overloads)
-
- * some `akka.http.javadsl.Http` method overloads with a materializer parameter (like `singleRequest`, `superPool`)
- * `akka.http.javadsl.HostConnectionPool.shutdown`
- * `akka.http.javadsl.model.HttpMethod.getRequestEntityAcceptance`
- * `akka.http.javadsl.model.HttpMethods.createCustom`
- * `akka.http.javadsl.settings.ConnectionPoolSettings.getTransport`
- * `akka.http.javadsl.*ConnectionContext.getDefaultPort`
-
- * some `akka.http.scaladsl.HttpExt` method overloads with a materializer parameter (like `singleRequest`, `superPool`)
- * `akka.http.scaladsl.Http#HostConnectionPool.shutdown`
- * `akka.http.scaladsl.HttpExt.outgoingConnectionUsingTransport`
- * `akka.http.scaladsl.UseHttp2` and related methods in *ConnectionContext and ConnectHttp*
- * `akka.http.scaladsl.model.HttpMethod.getRequestEntityAcceptance`
diff --git a/docs/src/main/paradox/migration-guide/migration-guide-2.4.x-10.0.x.md b/docs/src/main/paradox/migration-guide/migration-guide-2.4.x-10.0.x.md
deleted file mode 100644
index 7cab63897..000000000
--- a/docs/src/main/paradox/migration-guide/migration-guide-2.4.x-10.0.x.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# Migration Guide between Akka HTTP 2.4.x and 10.0.x
-
-## General notes
-
-Please note that Akka HTTP consists of a number of modules, most notably *akka-http-core*
-which is **stable** and won't be breaking compatibility without a proper deprecation cycle,
-and *akka-http* which contains the routing DSLs which is **experimental** still.
-
-The following migration guide explains migration steps to be made between breaking
-versions of the **experimental** part of Akka HTTP.
-
-@@@ note
-Please note that experimental modules are allowed (and are expected to) break compatibility
-in search of the best API we can offer, before the API is frozen in a stable release.
-
-Please read @extref[Binary Compatibility Rules](akka-docs:common/binary-compatibility-rules.html) to understand in depth what bin-compat rules are, and where they are applied.
-@@@
-
-## Akka HTTP 2.4.7 -> 2.4.8
-
-### `SecurityDirectives#challengeFor` has moved
-
-The `challengeFor` directive was actually more like a factory for @apidoc[HttpChallenge],
-thus it was moved to become such. It is now available as `akka.http.javadsl.model.headers.HttpChallenge#create[Basic|OAuth2]`
-for JavaDSL and `akka.http.scaladsl.model.headers.HttpChallenges#[basic|oAuth2]` for ScalaDSL.
-
-## Akka HTTP 2.4.8 -> 2.4.9
-
-### Java DSL Package structure changes
-
-We have aligned the package structure of the Java based DSL with the Scala based DSL
-and moved classes that were in the wrong or unexpected places around a bit. This means
-that Java DSL users must update their imports as follows:
-
-Classes dealing with unmarshalling and marshalling used to reside in `akka.http.javadsl.server`,
-but are now available from the packages `akka.http.javadsl.unmarshalling` and `akka.http.javadsl.marshalling`.
-
-`akka.http.javadsl.server.Coder` is now `akka.http.javadsl.coding.Coder`.
-
-`akka.http.javadsl.server.RegexConverters` is now `akka.http.javadsl.common.RegexConverters`.
-
-## Akka HTTP 2.4.11 -> 10.0.0
-
-### Java DSL @apidoc[PathDirectives] used Scala Function type
-
-The Java DSL for the following directives `pathPrefixText`, `rawPathPrefixTest`, `rawPathPrefix`, `pathSuffix`
-accidentally used the Scala function type instead of the `java.util.function.Function` functional interface,
-making them not usable in Java (unless compiled with Scala 2.12, which we're not yet shipping).
-
-These directives now accept the proper Java types. If you worked around this issue before, please remove your workaround and upgrade.
-Simply passing in a lambda expression will properly be expanded into the functional interface in these directives.
diff --git a/docs/src/main/paradox/release-notes/10.0.x.md b/docs/src/main/paradox/release-notes/10.0.x.md
deleted file mode 100644
index 6a0d600e7..000000000
--- a/docs/src/main/paradox/release-notes/10.0.x.md
+++ /dev/null
@@ -1,544 +0,0 @@
-# 10.0.x Release Notes
-
-## 10.0.15
-
-See the [announcement](https://akka.io/blog/news/2019/01/03/akka-http-10.0.15-released.html) and
-closed tickets on the [10.0.15 milestone](https://github.com/akka/akka-http/milestone/45?closed=1).
-
-This release contains backports for a number of relevant changes for the 10.1.x
-branch.
-
-### Notable Changes
-
-* Collision-resistant hashMap fixes [#2343](https://github.com/akka/akka-http/pull/2343)
-* TLS closing issue fixes [#2344](https://github.com/akka/akka-http/pull/2344)
-* Compilation error with Scala 2.12 [#2350](https://github.com/akka/akka-http/pull/2350)
-* Dependency upgrades [#2342](https://github.com/akka/akka-http/pull/2342)
-
-## 10.0.14
-
-See the [announcement](https://akka.io/blog/news/2018/09/06/akka-http-10.1.5-10.0.14-security-fix-released.html) and
-closed tickets on the [10.0.14 milestone](https://github.com/akka/akka-http/milestone/38?closed=1).
-
-This release fixes the [DoS vulnerability](https://doc.akka.io/docs/akka-http/current/security/2018-09-05-denial-of-service-via-decodeRequest.html)
-in the `decodeRequest` directive. Please update as soon as possible.
-
-### Migration Notes
-
-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 `decodeRequest` to 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 `HttpEntity.toStrict` or the `toStrictEntity` directive (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.
-
-### List of Changes
-
- * Restrict the maximum size of a request entity after uncompressing it with `decodeRequest` [#2137](https://github.com/akka/akka-http/issues/2137)
- * Restrict the maximum size of a request entity when reading it into memory with `toStrict` [#2186](https://github.com/akka/akka-http/pull/2186)
- * Support parameters for custom media types ([#2005](https://github.com/akka/akka-http/issues/2005))
-
-## 10.0.11
-
-See the [announcement](https://akka.io/blog/news/2017/12/01/akka-http-10.0.11-released.html) and
-closed tickets on the [10.0.11 milestone](https://github.com/akka/akka-http/milestone/31?closed=1).
-
-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](https://github.com/jonas), [@jlprat](https://github.com/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!
-
-### New caching module, akka-http-caching
-
-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](https://github.com/ben-manes/caffeine).
-
-Thanks a lot, [@tomrf1](https://github.com/tomrf1), [@jonas](https://github.com/jonas), [@ben-manes](https://github.com/ben-manes),
-[@ianclegg](https://github.com/ianclegg) for the fruitful discussions and for providing the implementation!
-
-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](https://github.com/akka/akka-http/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3At%3Acaching+label%3A%22help+wanted%22).
-We hope further collaboration within the community will help us stabilize the API.
-
-See the @ref[documentation](../common/caching.md) for more information.
-
-### Http Client Pool Infrastructure Rewrite
-
-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
-@apidoc[GraphStage] 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.
-
-### Incompatible changes to akka.http.{java,scala}dsl.coding classes
-
-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.DeflateDecompressorBase`,
-`akka.http.scaladsl.coding.DeflateCompressor`, and `akka.http.scaladsl.coding.GzipCompressor`. The actual codec APIs,
-`Gzip` and `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.
-
-### Cleanup of top-level Http APIs (slightly source incompatible)
-
-Several APIs in `Http` previously required an implicit `Materializer` argument (explicit in the Java version) where it
-was not necessary. In [#1464](https://github.com/akka/akka-http/issues/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.
-
-### List of Changes
-
-#### Improvements
-
-##### akka-http-core
-
- * New host connection pool infrastructure ([#1312](https://github.com/akka/akka-http/issues/1312))
- * Allow disabling of parsing to modeled headers ([#1550](https://github.com/akka/akka-http/issues/1550))
- * Convert RFC references in documents in model classes to scaladoc ([#1514](https://github.com/akka/akka-http/issues/1514))
- * Allow configuration of default http and https ports ([#1449](https://github.com/akka/akka-http/issues/1449))
- * Remove unnecessary implicit `materializer` parameter in several top-level @scala[@scaladoc[Http](akka.http.scaladsl.HttpExt)]@java[@javadoc[Http](akka.http.javadsl.Http)] entry point APIs ([#1464](https://github.com/akka/akka-http/issues/1464))
- * Add `X-Forwarded-Proto` and `X-Forwarded-Host` header models ([#1377](https://github.com/akka/akka-http/issues/1377))
- * Lookup predefined header parsers as early as possible ([#1424](https://github.com/akka/akka-http/issues/1424))
-
-##### akka-http
-
- * Add multiple file upload directive ([#1033](https://github.com/akka/akka-http/issues/1033))
- * Add Marshaller.oneOf(m1, m2) to JavaDSL ([#1551](https://github.com/akka/akka-http/issues/1551))
- * Improve performance of LineParser for SSE unmarshalling ([#1508](https://github.com/akka/akka-http/issues/1508))
- * Automatically probing and decompression support for zlib wrapped deflate streams ([#1359](https://github.com/akka/akka-http/issues/1359))
- * Simplify implicit parameter structure in FormFieldDirectives ([#541](https://github.com/akka/akka-http/issues/541))
- * Return BadRequest when size of FormData exceeds limit of `withSizeLimit` directive ([#1341](https://github.com/akka/akka-http/issues/1341))
-
-##### akka-http-testkit
-
- * Provide Dilated Timeouts for Java Testkit ([#1271](https://github.com/akka/akka-http/issues/1271))
- * Add more comprehensive description of the TestRoute run methods ([#1148](https://github.com/akka/akka-http/issues/1148))
- * Add a runWithRejections method to the Java TestRoute API ([#1148](https://github.com/akka/akka-http/issues/1148))
- * Support separation of route execution from checking in the Java DSL ([#1148](https://github.com/akka/akka-http/issues/1148))
-
-##### akka-http-caching
-
- * New module partly ported from spray-caching backed by caffeine ([#213](https://github.com/akka/akka-http/issues/213))
-
-##### Documentation
-
- * Ongoing work on consolidating Java and Scala documentation ([#1290](https://github.com/akka/akka-http/issues/1290))
- * Update Paradox and docs to use new features ([#1436](https://github.com/akka/akka-http/issues/1436))
-
-##### Build
-
- * Update to sbt 1.0.x
-
-#### Bug Fixes
-
-##### akka-http-core
-
- * Fix userinfo parsing to percent decode input in UriParser ([#1558](https://github.com/akka/akka-http/issues/1558))
- * Remove duplicate settings from akka.http.host-connection-pool.client so that akka.http.client will be picked up by default ([#1492](https://github.com/akka/akka-http/issues/1492))
- * Add minConnections modifier to javadsl ConnectionPoolSettings ([#1525](https://github.com/akka/akka-http/issues/1525))
- * Fix race condition in WebSocket switch leading to broken websocket connections in tests ([#1515](https://github.com/akka/akka-http/issues/1515))
-
-##### akka-http
-
- * Mark coding implementation classes as internal API ([#1570](https://github.com/akka/akka-http/issues/1570))
-
-## 10.0.10
-
-### Support for HTTP(S) proxies with Authorization
-
-It is now possible to connect to @ref[HTTP(S) Proxies](../client-side/client-transport.md)
-that require an authorization via an `Proxy-Authorization` header. This can be set up directly on the @apidoc[ClientTransport] object when configuring the proxy. ([#1213](https://github.com/akka/akka-http/issues/1213))
-
-### Documentation for HTTP 2 support (Preview)
-
-Server-side HTTP/2 support, currently available as a preview, has now been
-@ref[included in the documentation](../server-side/http2.md)
-([#1297](https://github.com/akka/akka-http/pull/1297))
-
-### Documentation consolidation
-
-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](https://github.com/akka/akka-http/issues/1290))
-
-### Improvements
-
-* (server) Better error reporting when failing to handle CONNECT requests ([#1315](https://github.com/akka/akka-http/issues/1315))
-* Add HttpApp.startServer(host, port, system) ([#1294](https://github.com/akka/akka-http/issues/1294))
-* Preserve the order of repeated parameters when retrieving query string as a multimap ([#1270](https://github.com/akka/akka-http/pull/1270))
-* Missing final boundary for empty multipart entities ([#1257](https://github.com/akka/akka-http/issues/1257))
-* Add Cache-Control 'immutable' value ([#1212](https://github.com/akka/akka-http/issues/1212))
-* Http2: Inbound flow control ([#737](https://github.com/akka/akka-http/issues/737))
-
-### Bugfixes
-
-* HttpChallenge rendering is broken if realm parameter is None ([#1295](https://github.com/akka/akka-http/issues/1295))
-* Logging with println in Http2ServerDemux ([#1275](https://github.com/akka/akka-http/issues/1275))
-* Incorrect request URIs with HTTP/2 ([#1274](https://github.com/akka/akka-http/issues/1274))
-* HttpResponseParser returns invalid status code for statuses without reason phrase ([#1251](https://github.com/akka/akka-http/issues/1251))
-* Ensure that no responses are lost when `host-connection-pool.idle-timeout` kicks in ([#1245](https://github.com/akka/akka-http/issues/1245))
-* Large response entity is truncated over https with 'Connection: close' header ([#1219](https://github.com/akka/akka-http/issues/1219))
-
-
-## 10.0.9
-
-This release fixes a regression in 10.0.8 that occurred when using media ranges and connecting to an HTTP server that fails to specify the charset in the `ContentType` [#1222](https://github.com/akka/akka-http/issues/1222).
-
-Additionally, support for HTTP status code 418 has been introduced [#1206](https://github.com/akka/akka-http/issues/1206)
-
-## 10.0.8
-
-### HTTP(S) Proxy Support
-
-Long awaited support for configuring an @ref[HTTP(S) CONNECT Proxy](../client-side/client-transport.md#use-https-proxy-with-http-singlerequest)
-for the client has arrived. Thanks a lot, [Michal Sitko (@note)](https://github.com/note), who implemented the feature.
-
-Support for proxies that require authentication is yet to be implemented and is tracked by the ticket [#1213](https://github.com/akka/akka-http/issues/1213)
-
-### Ability to express textual content types with missing character set
-
-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 `charset` attribute.
-
-From now on, content types missing a charset can be both parsed and expressed directly, using the new
-`ContentType.WithMissingCharset` trait/class.
-
-- For incoming Content-Type headers with values missing a charset, such as `text/plain`, the header
- `ContentType` will 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. ```MediaTypes.`text/plain`.withMissingCharset```
- (scala) or `MediaTypes.TEXT_PLAIN.toContentTypeWithMissingCharset()` (java).
-
-*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
-`ContentType.WithMissingCharset` case.
-
-### Server-Sent Events Support
-
-Support for Server-Sent events was added by merging akka-sse project by [@hseeberger](https://github.com/hseeberger). Thank you very much, Heiko!
-
-### List of Changes
-
-#### Improvements
-
-##### akka-http-core
-
-* HTTP(S) proxy support ([#192](https://github.com/akka/akka-http/issues/192))
-* Allow '=' in query param values in relaxed mode ([#1120](https://github.com/akka/akka-http/issues/1120))
-
-##### akka-http
-
-* Add support for Server-Sent Events ([#669](https://github.com/akka/akka-http/issues/669))
-* Add support for textual content types with missing character set ([#1134](https://github.com/akka/akka-http/issues/1134))
-
-##### akka-http-testkit
-
-* Remove unnecessary dependency to ScalaTest from JUnitSuiteLike ([#1147](https://github.com/akka/akka-http/issues/1147))
-
-##### Documentation
-
-* Document pluggable client transport infrastructure and HTTP(S) proxy support ([#192](https://github.com/akka/akka-http/issues/192))
-* Reference security announcements and release notes in ToC ([#1199](https://github.com/akka/akka-http/issues/1199))
-
-#### Bug Fixes
-
-##### akka-http-core
-
-* Parse Websocket headers according to the set header processing mode ([#1166](https://github.com/akka/akka-http/issues/1166))
-* Fix a regression which caused the idle-timeout on server side not to function properly ([#1012](https://github.com/akka/akka-http/issues/1012))
-* Add a special handling of the charset parameter in Accept header when comparing media types ([#1139](https://github.com/akka/akka-http/issues/1139))
-* Use ws(s) scheme instead of http(s) when calculating effective websocket request URIs ([#909](https://github.com/akka/akka-http/issues/909))
-
-## 10.0.7
-
-### New Seed Templates for Akka HTTP Apps
-
-We prepared new seed templates for starting out with Akka HTTP using the [Java DSL](https://github.com/akka/akka-http-java-seed.g8)
-as well as [Scala DSL](https://github.com/akka/akka-http-scala-seed.g8). 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.
-
-### New Path Directive `ignoreTrailingSlash`
-
-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 @ref[documentation page](../routing-dsl/directives/path-directives/ignoreTrailingSlash.md).
-
-### List of Changes
-
-#### Improvements
-
-##### akka-http
- * Added new Path Directive `ignoreTrailingSlash` ([#880](https://github.com/akka/akka-http/issues/880))
- * Prepared new seed templates for Akka HTTP apps (for both [Java DSL](https://github.com/akka/akka-http-java-seed.g8) and [Scala DSL](https://github.com/akka/akka-http-scala-seed.g8)) ([1137](https://github.com/akka/akka-http/issues/1137) & [1055](https://github.com/akka/akka-http/issues/1055))
- * Migrated to the new docs theme (same as Akka) ([#1129](https://github.com/akka/akka-http/issues/1129))
- * (ApiMayChange) `HttpApp#route` method was renamed to `routes` to highlight it is "all the routes" ([#953](https://github.com/akka/akka-http/issues/953))
-
-#### akka-http2-support
- * Synthetic Remote-Address header setting is now honored in HTTP2 server blueprint ([#1088](https://github.com/akka/akka-http/issues/1088))
-
-#### Bug Fixes
-
-##### General
- * OSGi Import-Package ranges have been fixed to allow Akka 2.5.x ([#1097](https://github.com/akka/akka-http/issues/1097))
-
-##### akka-http-core
- * Dates in RFC1123 format with single-digit-day are now properly parsed ([#1110](https://github.com/akka/akka-http/issues/1110))
-
-
-## 10.0.6
-
-See the [announcement](https://akka.io/blog/news/2017/05/03/akka-http-10.0.6-released.html) and
-closed tickets on the [10.0.6 milestone](https://github.com/akka/akka-http/milestone/23?closed=1).
-
-10.0.6 is a security and maintenance release in the stable 10.0.x series of Akka HTTP.
-
-@@@ warning
-
-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
-@ref[details](../security/2017-05-03-illegal-media-range-in-accept-header-causes-stackoverflowerror.md) for more information.
-Please update as soon as possible.
-
-@@@
-
-### List of Changes
-
-#### Improvements
-
-##### akka-http-core
- * Make response parser more relaxed on accepting status line without reason message ([#981](https://github.com/akka/akka-http/issues/981))
- * Use media type parameters in content negotiation ([#963](https://github.com/akka/akka-http/issues/963))
- * Small performance improvements ([#999](https://github.com/akka/akka-http/issues/999), [#1032](https://github.com/akka/akka-http/issues/1032))
- * Added `HttpMessage.transformEntityDataBytes` ([#771](https://github.com/akka/akka-http/issues/771))
- * Allow binding server with HTTP/2 support via configuration flag with `Http().bindAndHandleAsync` ([#463](https://github.com/akka/akka-http/issues/463))
-
-##### akka-http
-
- * Make marshaller composition more lazy to prevent redundant marshalling when using `Marshaller.oneOf` ([#1019](https://github.com/akka/akka-http/issues/1019))
- * Allow Java-implemented ContentTypeResolver ([#360](https://github.com/akka/akka-http/issues/360))
- * Java DSL routing `complete` now has override that takes @apidoc[ResponseEntity] as a parameter instead of @apidoc[RequestEntity](RequestEntity) ([#982](https://github.com/akka/akka-http/issues/982))
- * Improved usage and documentation of Encoder / Decoder on the Scala and Java side ([#771](https://github.com/akka/akka-http/issues/771))
-
-##### akka-http2-support
-
- * Refactoring: move handling of per-stream frames to dedicated state handlers ([#1064](https://github.com/akka/akka-http/issues/1064))
-
-##### Documentation
-
- * Provide Decoding Response example for Java ([#760](https://github.com/akka/akka-http/issues/760))
- * Add Java example to extract header value with default value ([#639](https://github.com/akka/akka-http/issues/639))
- * Add HTTP custom method example ([#954](https://github.com/akka/akka-http/issues/954))
- * Smaller fixes and additions
-
-##### Build + Infrastructure
-
- * Add OSGi to project in order to release each project with OSGi bundle headers ([#574](https://github.com/akka/akka-http/issues/574))
- * Rename root project to 'akka-http-root' ([#1030](https://github.com/akka/akka-http/issues/1030))
-
-#### Bug Fixes
-
-##### akka-http-core
-
- * Ignore unsupported `*/xyz` media types ([#1072](https://github.com/akka/akka-http/issues/1072))
- * Exclude port when rendering X-Forwarded-For and X-Real-Ip headers ([#440](https://github.com/akka/akka-http/issues/440))
- * Fix NPE when accessing static Java constant fields ([#936](https://github.com/akka/akka-http/issues/936))
- * Make sure pool log messages have "PoolGateway" set as logClass for easier filtering ([#1013](https://github.com/akka/akka-http/issues/1013))
-
-##### akka-http
-
- * Move special non-2xx handling from RequestContextImpl to fromStatusCodeAndHeadersAndValue marshaller ([#1072](https://github.com/akka/akka-http/issues/1072))
- * Handle failure while parsing the URI in parameter extraction ([#1043](https://github.com/akka/akka-http/issues/1043))
- * Make `extractStrictEntity` provide strict entity for inner routes ([#961](https://github.com/akka/akka-http/issues/961))
- * Enable javadsl to unmarshal with default `ExecutionContext` ([#967](https://github.com/akka/akka-http/issues/967))
- * Smaller fixes for @apidoc[HttpApp]
-
-##### akka-http2-support
-
- * Fix memory leak in ALPN switcher ([#886](https://github.com/akka/akka-http/issues/886))
-
-## 10.0.5
-
-See the [announcement](https://akka.io/blog/news/2017/03/17/akka-http-10.0.5-released.html) and
-closed tickets on the [10.0.5 milestone](https://github.com/akka/akka-http/milestone/22?closed=1).
-
-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.
-
-### List of Changes
-
-#### Improvements
-
-##### akka-http-core
- * New docs and API for registering custom headers with JavaDSL ([#761](https://github.com/akka/akka-http/issues/761))
- * Ssl-config upgraded to 0.2.2, allows disabling/changing hostname verification ([#943](https://github.com/akka/akka-http/issues/943))
- * Don’t depend on Akka internal APIs, become compatible with Akka 2.5 ([#877](https://github.com/akka/akka-http/issues/877))
- * Make default exception handler logging more informative ([#887](https://github.com/akka/akka-http/issues/887))
-
-##### akka-http
- * Unmarshal.to now uses the materializer ExecutionContext if no other provided implicitly ([#947](https://github.com/akka/akka-http/pull/947))
-
-#### Bug Fixes
-
-##### akka-http-core
- * Prevent longer-than-needed lingering streams by fixing DelayCancellationStage ([#945](https://github.com/akka/akka-http/issues/945))
-
-##### akka-http
- * Avoid redirect-loop when redirectToNoTrailingSlashIfPresent was used for root path ([#878](https://github.com/akka/akka-http/issues/878))
-
-### Compatibility notes
-
-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.
-
-
-## 10.0.4
-
-See the [announcement](https://akka.io/blog/news/2017/02/23/akka-http-10.0.4-released.html) and
-closed tickets on the [10.0.4 milestone](https://github.com/akka/akka-http/milestone/21?closed=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](https://github.com/akka/akka-http/issues/851) for more information.
-
-### List of Changes
-
-#### Improvements
-
-##### akka-http-core
- * Http message and header parser now also accepts LF as end of line (as recommended in the spec) ([#106](https://github.com/akka/akka-http/issues/106))
-
-##### akka-http
- * @apidoc[HttpApp] now directly extends from Directives ([#875](https://github.com/akka/akka-http/issues/875))
- * Added `HttpApp.startServer(host, port)` for even simpler startup. ([#873](https://github.com/akka/akka-http/issues/873))
-
-##### akka-http2-support
- * Multiplexer infrastructure was rewritten to support plugable @javadoc[StreamPrioritizer](akka.http.impl.engine.http2.StreamPrioritizer) (not yet surfaced in user API) ([f06ab40](https://github.com/akka/akka-http/commit/f06ab40))
-
-##### Documentation
- * New documentation page about how to deal with the client-side `max-open-requests` exception ([39f36dd](https://github.com/akka/akka-http/commit/39f36dd))
- * Lots of small cleanups and improvements
-
-#### Bug Fixes
-
-##### akka-http-core
- * Fix a regression introduced in 10.0.3 that might lead to memory leaking after a server connection has been closed. ([#851](https://github.com/akka/akka-http/issues/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 `curl`) ([#516](https://github.com/akka/akka-http/issues/516))
-
-##### Build + Testing Infrastructure
- * Updated Akka dependency to Akka 2.4.17. ([#858](https://github.com/akka/akka-http/issues/858))
- * Use `.dilated` for tests for better stability. ([#194](https://github.com/akka/akka-http/issues/194))
- * Fix MiMa to actually check compatibility against the latest released versions. ([#870](https://github.com/akka/akka-http/issues/870))
- * Throughout the code base `@InternalApi`, `@ApiMayChange`, and `@DoNotInherit` annotations have been added
- to give hints about the stability of interfaces. ([#727](https://github.com/akka/akka-http/issues/727))
-
-## 10.0.3
-
-See the [announcement](https://akka.io/blog/news/2017/01/26/akka-http-10.0.3-released.html) and
-closed tickets on the [10.0.3 milestone](https://github.com/akka/akka-http/milestone/19?closed=1).
-
-This release contains mostly bug fixes, a huge number of contributed documentation fixes and
-small improvements.
-
-### HttpApp
-
-A notable new feature is the experimental @apidoc[HttpApp] feature (long time users may know it from spray). It allows
-to create an Akka HTTP server with very little boilerplate. See its [documentation](https://doc.akka.io/docs/akka-http/10.1/routing-dsl/HttpApp.html). Thanks a lot, [@jlprat](https://github.com/jlprat) for
-contributing this feature and carrying through the PR with the most comments so far.
-
-### Changed semantics
-
-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.toString` now doesn't render leading double slashes any more ([#784](https://github.com/akka/akka-http/issues/784))
- * request URIs for requests coming in for a server set up to use TLS now carry the `https` scheme ([#658](https://github.com/akka/akka-http/issues/658))
-
-### List of changes
-
-#### Improvements
-
-##### akka-http-core:
-
- * Optimize frame creation for streamed WS messages ([#748](https://github.com/akka/akka-http/issues/748))
-
-##### akka-http:
-
- * Provide HttpApp API for Scala and Java ([#156](https://github.com/akka/akka-http/issues/156))
- * Add Java-side mapRejectionResponse ([#593](https://github.com/akka/akka-http/issues/593))
- * Add Composing directives java (`anyOf`, `allOf`). ([#620](https://github.com/akka/akka-http/issues/620))
- * Add Unmarshaller.andThen to combine two Unmarshallers ([#691](https://github.com/akka/akka-http/issues/691))
-
-##### akka-http2-support:
-
- * Lots of larger and smaller improvements to Http2 support
-
-#### Bug Fixes
-
-##### akka-http-core:
-
- * Allow Java bind API to specify port zero ([#660](https://github.com/akka/akka-http/issues/660))
- * Fix ConnectHttp.toHostHttps when no scheme is given
- * Exclude leading double slash from Uri.Authority.toString ([#784](https://github.com/akka/akka-http/issues/784))
- * Basic auth fix according to rfc7617 - 'charset' auth-param ([#716](https://github.com/akka/akka-http/issues/716))
- * Provide correct scheme in request URI for TLS connections ([#658](https://github.com/akka/akka-http/issues/658))
- * Prevent "Connection closed by peer" errors during connection closure ([#459](https://github.com/akka/akka-http/issues/459))
-
-##### akka-http:
-
- * Fix stream marshalling, better errors, more examples ([#424](https://github.com/akka/akka-http/issues/424))
- * Don't ignore failed future for NoContent responses ([#589](https://github.com/akka/akka-http/issues/589))
- * Deprecate wrongly spelled method `Unmarshaller.unmarshall`
- * Match path maps in order of longest matching key prefix ([#394](https://github.com/akka/akka-http/issues/394))
- * Don't leak Scala classes in java Unmarshaller ([#604](https://github.com/akka/akka-http/issues/604))
-
-##### akka-http-testkit:
-
- * Add support for Specs2 in testkit ([#485](https://github.com/akka/akka-http/issues/485))
-
-##### akka-http-spray-json:
-
- * Fix spray-json unmarshalling of 4-byte UTF-8 characters AKA "the 😁 fix" ([#691](https://github.com/akka/akka-http/issues/691))
- * Updated spray-json dependency to 1.3.3
-
-#### Documentation
-
- * 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](https://github.com/akka/akka-http/issues/726))
-
-
-## 10.0.2
-
-Security patch to prevent denial-of-service due to memory leak in server infrastructure.
-
-See the [announcement](https://akka.io/blog/news/2017/01/23/akka-http-10.0.2-security-fix-released.html),
-@ref[Details](../security/2017-01-23-denial-of-service-via-leak-on-unconsumed-closed-connections.md) and
-[changes](https://github.com/akka/akka-http/compare/v10.0.1...v10.0.2).
-
-## 10.0.1
-
-See the [announcement](https://akka.io/blog/news/2016/12/22/akka-http-10.0.1-released.html) and
-closed tickets on the [10.0.1 milestone](https://github.com/akka/akka-http/milestone/17?closed=1)
-
-## 10.0.0
-
-See the [announcement](https://akka.io/blog/news/2016/11/22/akka-http-10.0.0-released.html) and
-closed tickets on the [10.0.0 milestone](https://github.com/akka/akka-http/milestone/14?closed=1)
diff --git a/docs/src/main/paradox/release-notes/10.1.x.md b/docs/src/main/paradox/release-notes/10.1.x.md
deleted file mode 100644
index 6d76bf4e5..000000000
--- a/docs/src/main/paradox/release-notes/10.1.x.md
+++ /dev/null
@@ -1,790 +0,0 @@
-# 10.1.x Release Notes
-
-## 10.1.15
-
-This release is an important security fix release, backporting fixes from 10.2.7 to the 10.1.x line of releases. Note,
-that we do not plan any further releases for 10.1.x, so please consider upgrading soon to the latest supported release line,
-10.2.x. Due to our binary compatibility guarantees, as long as no deprecated methods were used, 10.2.x should be a drop-in
-replacement in 10.1.x projects, even when transitive dependencies depended on 10.1.x.
-
-Most importantly, we fixed a problem with parsing headers containing `comment` elements ([#3918](https://github.com/akka/akka-http/issues/3918)).
-The HTTP spec allows arbitrary
-nesting of those elements, e.g. in the `User-Agent` header. When such a header is parsed, an Akka HTTP application may
-fail fatally with a `StackOverflowError`. Akka HTTP 10.2.7 mitigates this issue by conservatively limiting the allowed
-depth of `comment` elements in headers.See @ref[the advisory for CVE-2021-42697](../security/2021-CVE-2021-42697-stack-overflow-parsing-user-agent.md)
-for more information about this security issue.
-
-Another issue has been fixed in relation to header rendering ([#3717](https://github.com/akka/akka-http/issues/3717)).
-Akka HTTP does not validate that header values (or keys)
-are well-formed when those are provided as Strings (e.g. in a `RawHeader`). In particular, HTTP headers are not allowed
-to contain the special characters `'\r'` or `'\n'` which are used to delineate headers in an HTTP message. Before 10.2.7,
-Akka HTTP would naively render those broken header values leading to broken HTTP messages. The generation of headers is
-usually in complete control of the application. However, an application may accidentally pass incoming unvalidated user
-data to response headers. In such a case, a remote user might be able to inject line terminators into the response headers
-leading to invalid or misleading HTTP response messages. Depending on the server setup, this can be a building block for
-severe attacks.
-
-To mitigate this issue, Akka HTTP now discards outgoing headers containing line terminators and logs a warning. Users
-are encouraged to be on the watch when creating headers (or any kind of outgoing data) from unvalidated user input as this
-is a common vector for different kinds of attacks.
-
-A few smaller issues have been backported as well, see below.
-
-#### akka-http-core
-
-* Discard outgoing headers containing line breaks [#3922](https://github.com/akka/akka-http/pull/3922)
-* Limit comment nesting in header parser [#3941](https://github.com/akka/akka-http/pull/3941)
-* Add pool keep-alive-timeout [#3816](https://github.com/akka/akka-http/pull/3816)
-* Don't send '100 Continue' if 'Content-Length' header is 0, doesn't exist or data got send early [#3787](https://github.com/akka/akka-http/pull/3787)
-* Update to Scala 2.13.7 [#3945](https://github.com/akka/akka-http/pull/3945)
-* Fix MessageSpec with higher test.timefactor values [#3880](https://github.com/akka/akka-http/pull/3880)
-
-## 10.1.14
-
-This release fixes [CVE-2021-23339](https://nvd.nist.gov/vuln/detail/CVE-2021-23339), a vulnerability regarding interpretation of `Transfer-Encoding` headers. See
-@ref:[Incorrect Handling Of Transfer-Encoding Header](../security/2021-02-24-incorrect-handling-of-Transfer-Encoding-header.md).
-
-The vulnerability cannot be exploited using just Akka HTTP itself. Instead, Akka HTTP must be use as a proxy and the downstream server must be vulnerable itself, so
-that the proxy and the downstream server disagree on how to interpret a malformed request containing both `Transfer-Encoding` and `Content-Length` headers potentially
-leading to a "Request Smuggling" vulnerability. If you are using Akka HTTP as a reverse proxy, make sure to upgrade to the latest version.
-
-Starting from this version, only a single `Transfer-Encoding: chunked` header is allowed. HTTP/1.1 specifies other encodings, however, those are not supported or
-implemented in Akka HTTP. Formerly, Akka HTTP would just pass on unsupported `Transfer-Encoding` headers to the user which lead to the above security issue. Since
-Akka HTTP implements the "Transfer" part of the protocol, it seems reasonable to lock down allowed values for `Transfer-Encoding` to prevent security issues like this.
-Please let us know if this leads to compatibility problems with your software.
-
-## 10.1.13
-
-### Changes since 10.1.12
-
-#### akka-http-core
-
-* Don't fail pool slot after previous connection failed in special condition [#3021](https://github.com/akka/akka-http/pull/3021)
-* Make HttpEntity.Strict.discardBytes a no-op [#3329](https://github.com/akka/akka-http/pull/3329)
-
-## 10.1.12
-
-### ALPN support in JDK >= 8u252
-
-ALPN support was backported to recent JDK 8 updates. When using HTTP2 support with these JDKs, the `jetty-alpn-agent`
-is not needed anymore. If you want to run on older and newer JDKs with the same command line, make sure to use the
-most recent version of `jetty-alpn-agent` which will automatically disable itself for newer JDKs.
-
-### Changes since 10.1.11
-
-#### akka-http-core
-
-* Fix EOL detection for body part parsing [#3144](https://github.com/akka/akka-http/pull/3144)
-* Fix parsing of partly cached headers with UTF-8 values [#3096](https://github.com/akka/akka-http/pull/3096)
-* Fix cancellation race conditions on the client-side [#2965](https://github.com/akka/akka-http/pull/2965)
-* Make sure to cancel response entity on failure [#3046](https://github.com/akka/akka-http/pull/3046)
-* Make sure reference.conf files end with a new-line character.[#2841](https://github.com/akka/akka-http/pull/2841)
-* Only catch NonFatal Exceptions while parsing responses [#2853](https://github.com/akka/akka-http/pull/2853)
-* Add the remote address in parse errors when possible (when remote-address-header is enabled) [#2899](https://github.com/akka/akka-http/pull/2899)
-* Silence outgoing request stream error (and make it more useful) [#2816](https://github.com/akka/akka-http/pull/2816)
-* Identify Content-Type `charset` parameter even if not lower case [#2926](https://github.com/akka/akka-http/pull/2926)
-* Prevent initialization NPE which might fail all retries quickly [#2958](https://github.com/akka/akka-http/pull/2958)
-* Add exclusion for Extension issues when building against Akka 2.6 [#2945](https://github.com/akka/akka-http/pull/2945)
-* Nest correctly in NewHostConnectionPool [#2964](https://github.com/akka/akka-http/pull/2964)
-
-#### akka-http-marshallers
-
-* Jackson: better JSON validation error when unmarshalling [#2901](https://github.com/akka/akka-http/pull/2901)
-
-#### docs
-
-* Small typo in docs/src/main/paradox/common/marshalling.md [#2864](https://github.com/akka/akka-http/pull/2864)
-* Add warning on usage on extractClientIP [#2922](https://github.com/akka/akka-http/pull/2922)
-* Show RequestBuilding in client examples [#2968](https://github.com/akka/akka-http/pull/2968)
-* Fix project-info links to API docs [#2857](https://github.com/akka/akka-http/pull/2857)
-
-#### akka-http2-support
-
-* Support ALPN natively on JDK >= 8u252 [#3125](https://github.com/akka/akka-http/pull/3125)
-* Gracefully discard unsupported h2 SETTINGS [#3053](https://github.com/akka/akka-http/pull/3053)
-* Potential fix for idle timeouts in http2 [#2776](https://github.com/akka/akka-http/pull/2776)
-* Fix HeaderCompression updating table size without giving notice to peer [#2888](https://github.com/akka/akka-http/pull/2888)
-
-## 10.1.11
-
-### Changes since 10.1.10
-
-#### akka-http-core
-
-* Hide body data from `Http.Strict#toString` [#2737](https://github.com/akka/akka-http/pull/2737)
-* Support chunked trailing headers in `transformDataBytes` [#2748](https://github.com/akka/akka-http/pull/2748)
-* Fix race condition in ConnectionPoolSpec, [#2796](https://github.com/akka/akka-http/pull/2796)
-* Improve WS masking performance [#2801](https://github.com/akka/akka-http/pull/2801)
-* Update naming for status codes 413, 414, 416 and 505 [#2808](https://github.com/akka/akka-http/pull/2808)
-* Improve "Entity stream truncation" error message [#2789](https://github.com/akka/akka-http/pull/2789)
-* Silence noisy pool idle timeout messages [#2816](https://github.com/akka/akka-http/pull/2816)
-* Improve `EntityStreamSizeException` message [#2823](https://github.com/akka/akka-http/pull/2823)
-* Tone down the connection failure warning [#2837](https://github.com/akka/akka-http/pull/2837)
-
-#### akka-http
-
-* fix default rejection message for unsupported content type [#2804](https://github.com/akka/akka-http/pull/2804)
-
-#### akka-http2-support
-
-* Allow sending an ack SETTINGS frame immediately [#2735](https://github.com/akka/akka-http/pull/2735)
-* Make sure all substreams are closed when connection is torn down[#2777](https://github.com/akka/akka-http/pull/2777)
-* Fix HTTP/1.1 ALPN negotiation [#2791](https://github.com/akka/akka-http/pull/2791)
-
-#### docs
-
-* Fix `authorizeAsync` documentation [#2746](https://github.com/akka/akka-http/pull/2746)
-* Doc fix for regex paths from Java [#2749](https://github.com/akka/akka-http/pull/2749)
-* Fix/amend 10.1.10 release notes formatting[#](https://github.com/akka/akka-http/pull/)
-* Typed sample polish [#2784](https://github.com/akka/akka-http/pull/2784)
-
-#### build
-
-* Collapse PR validation report for less clutter [#2707](https://github.com/akka/akka-http/pull/2707)
-* Update to latest Scala versions [#2756](https://github.com/akka/akka-http/pull/2756)
-* Allow deployRsync for publishing snapshot docs [#2821](https://github.com/akka/akka-http/pull/2821)
-* Use more resilient checking for Scala 2.13 in Mima [#2820](https://github.com/akka/akka-http/pull/2820)
-* Enable coursier [#2835](https://github.com/akka/akka-http/pull/2835)
-
-## 10.1.10
-
-### Migration notes
-
-[RFC 7231](https://tools.ietf.org/html/rfc7231#section-6.3.6) dictates an HTTP response with status code 205 ('Reset Content') is not allowed to have an entity body. Since [#2686](https://github.com/akka/akka-http/pull/2686) we enforce this restriction, so if you (incorrectly) produced such responses you will have to either remove the entity body or select a different status code.
-
-### Changes since 10.1.9
-
-For a full overview you can also see the [10.1.10 milestone](https://github.com/akka/akka-http/milestone/51?closed=1):
-
-##### akka-http-core
-
-* Fix 205 HTTP status not to contain any HTTP entity [#2686](https://github.com/akka/akka-http/pull/2686)
-* Support multiple subprotocols in WebSocket handshake [#2606](https://github.com/akka/akka-http/issues/2606)
-* Add `endsWith` predicate to `Uri.Path` [#2480](https://github.com/akka/akka-http/pull/2480)
-* Handle unrecognized status codes according to spec [#2503](https://github.com/akka/akka-http/pull/2503)
-* Better error handling on server when response entity stream fails [#2627](https://github.com/akka/akka-http/pull/2627)
-* Force connection closure when pool is stopped [#2631](https://github.com/akka/akka-http/pull/2631)
-* Enable `log-unencrypted-network-bytes` also for websocket client traffic [#2647](https://github.com/akka/akka-http/pull/2647)
-* Add modeled header for Content-Location [#2540](https://github.com/akka/akka-http/pull/2540)
-* Streamed response processing performance improvements [#2645](https://github.com/akka/akka-http/pull/2645)
-* Make custom MediaType and MediaRange.matches case-insensitive [#2126](https://github.com/akka/akka-http/pull/2126)
-* Avoid prematurely closing long-lived requests [#1847](https://github.com/akka/akka-http/issues/1847)
-* Avoid reliance on deprecated ActorPublisher, as this is no longer available in Akka 2.6 [#2617](https://github.com/akka/akka-http/issues/2617)
-
-##### akka-http
-
-* More precise IllegalArgumentException catch for case class extraction [#2593](https://github.com/akka/akka-http/pull/2593)
-* Add logging unsupported content type [#2512](https://github.com/akka/akka-http/pull/2512)
-* Widen JavaUUID regexp's [#2624](https://github.com/akka/akka-http/pull/2624)
-
-##### akka-http2-support
-
-* Support HTTP2 in cleartext (h2c) via Upgrade from HTTP1 [#2464](https://github.com/akka/akka-http/pull/2464)
-* Backpressure incoming frames when too many outgoing control frames are buffered [#2706](https://github.com/akka/akka-http/pull/2706)
-* Fix receiving HEADERS with more than one CONTINUATION frame [#2701](https://github.com/akka/akka-http/pull/2701)
-
-## 10.1.9
-
-10.1.9 is the tenth release in the 10.1.x series of Akka HTTP. See the [announcement](https://akka.io/blog/news/2019/07/17/akka-http-10.1.9-released.html) and the full list of changes below.
-
-### Changes since 10.1.8
-
-For a full overview you can also see the [10.1.9 milestone](https://github.com/akka/akka-http/milestone/49?closed=1):
-
-##### akka-http-core
-
-* Don't use a https connection pool for http connections (javadsl) [#2562](https://github.com/akka/akka-http/pull/2562)
-
-##### akka-http
-
-* Add String-to-UUID unmarshaller to the predefined Scala unmarshallers [#2505](https://github.com/akka/akka-http/pull/2505)
-* Improve validation in uuid unmarshaller [#2569](https://github.com/akka/akka-http/pull/2569/)
-* Fix missing header rejection for custom headers [#2487](https://github.com/akka/akka-http/issues/2487)
-* Fix case of nested FormField if first formField usage is with single parameter [#2524](https://github.com/akka/akka-http/pull/2543)
-* Support 'streaming back' an uploaded file [#2582](https://github.com/akka/akka-http/pull/2582)
-
-
-##### akka-http2-support
-
-* Allow HTTP/1.1 and HTTP/2 on the same port without TLS or Upgrade headers [#2543](https://github.com/akka/akka-http/pull/2543)
-* Retired the UseHttp2 setting: when enabled, HTTP/2 is now always available [#2557](https://github.com/akka/akka-http/pull/2557)
-* Add akka.http.server.http2.log-frames for verbose frame logging for debugging purposes [#2561](https://github.com/akka/akka-http/pull/2561)
-* Fix reception of unexpected mid-stream HEADERS frame with endStream=false [#2557](https://github.com/akka/akka-http/pull/2557)
-* Close HTTP/2 streams earlier [#2551](https://github.com/akka/akka-http/issues/2551)
-
-##### akka-http-caching
-
-* Upgrade caffeine to 2.7 which removes need for dummyLoader [#2443](https://github.com/akka/akka-http/issues/2443)
-* Add Cache.put method to refresh cached value without removing it first [#2385](https://github.com/akka/akka-http/issues/2385)
-
-## 10.1.8
-
-10.1.8 is the ninth release in the 10.1.x series of Akka HTTP. See the [announcement](https://akka.io/blog/news/2019/03/25/akka-http-10.1.8-released.html) and the full list of changes below.
-
-### Changes since 10.1.7
-
-For a full overview you can also see the [10.1.8 milestone](https://github.com/akka/akka-http/milestone/47?closed=1):
-
-#### Improvements
-
-##### akka-http-core
-
-* Do not include error details in HTTP response [#2314](https://github.com/akka/akka-http/pull/2314)
-* More reliable detection of HTTPS => HTTP connection attempts [#1886](https://github.com/akka/akka-http/pull/1886)
-* use JDK9+ ALPN support if available [#2280](https://github.com/akka/akka-http/issues/2280)
-* Allow overriding of User-Agent header with custom RawHeader [#2277](https://github.com/akka/akka-http/issues/2277)
-* Allow overriding of Host header with custom RawHeader [#2436](https://github.com/akka/akka-http/issues/2436)
-* Support for scala 2.13.0-M5 [#2298](https://github.com/akka/akka-http/pull/2298)
-* Optimize HttpMessageParser.push code path [#2450](https://github.com/akka/akka-http/pull/2450)
-* Optimize RequestTimeout support for the common case [#2452](https://github.com/akka/akka-http/pull/2452)
-* Use static scanning when searching for well-known ContentType for rendering [#2453](https://github.com/akka/akka-http/pull/2453)
-* Add new option to close connections after a period of time [#2016](https://github.com/akka/akka-http/pull/2016)
-
-##### akka-http
-
-* Change GZip and Deflate compression level and makes it configurable [#2318](https://github.com/akka/akka-http/issues/2318)
-* Provide configuration settings for client SSE limits [#2193](https://github.com/akka/akka-http/pull/2193)
-* Oversized requests should return 413 and not 500 [#358](https://github.com/akka/akka-http/issues/358)
-* Don't repeat query of target URI in error response [#2397](https://github.com/akka/akka-http/issues/2397)
-
-##### docs
-
-* Improve `onSuccess` docs to explain Tupler magic [#993](https://github.com/akka/akka-http/issues/993)
-* Add links endorsing support projects [#1968](https://github.com/akka/akka-http/issues/1968)
-
-##### akka-http2-support
-
-* Allow (but ignore) RST and WindowUpdate frames on closed HTTP/2 streams [#2457](https://github.com/akka/akka-http/pulls/2457)
-* Clean up ALPN when the stream is stopped [#2471](https://github.com/akka/akka-http/pulls/2471)
-
-#### Bug fixes
-
-* Response shouldn't override connection header when connection is force-closed [#2403](https://github.com/akka/akka-http/issues/2403)
-* Disable to append charset=UTF-8 by default in `Content-Type: application/x-www-form-urlencoded` FormData [#91](https://github.com/akka/akka-http/issues/91)
-* Fix int overflow in sliceBytesTransformer [#2440](https://github.com/akka/akka-http/issues/2440)
-* LogRequest not respecting LogLevel in Java [#2418](https://github.com/akka/akka-http/issues/2418)
-
-
-## 10.1.7
-
-10.1.7 is the eighth release in the 10.1.x series of Akka HTTP. See the [announcement](https://akka.io/blog/news/2019/01/04/akka-http-10.1.7-released.html) and the full list of changes below.
-
-### Changes since 10.1.6
-
-For a full overview you can also see the [10.1.7 milestone](https://github.com/akka/akka-http/milestone/46?closed=1):
-
- * Media types were added for `application/problem+json` and `application/problem+xml` ([RFC 7807](https://tools.ietf.org/html/rfc7807)) [#2323](https://github.com/akka/akka-http/pull/2323)
- * Media types were added for `font/woff` and `font/woff2` [#2330](https://github.com/akka/akka-http/issues/2330)
- * A checker was added that produces a run-time warning when different versions of Akka HTTP modules are found on the classpath [#2335](https://github.com/akka/akka-http/issues/2335)
- * Various dependencies were updated [#2328](https://github.com/akka/akka-http/pull/2328)
-
-## 10.1.6
-
-10.1.6 is the seventh release in the 10.1.x series of Akka HTTP. See the full list of changes below.
-
-### Migration Notes
-
- * akka-http now requires to be run with Akka 2.5.19+ to support JDK 11 from Java.
- * `RoutingSettings` were moved to `akka-http` from `akka-http-core` (where they logically belong). Make sure to depend
- on `akka-http` when referencing this class (which is very likely because it couldn't be used otherwise).
- * `akka-stream-testkit` is now a only a provided dependency for `akka-http-testkit`, if you use `akka-http-testkit` also
- add a dependency to `akka-stream-testkit` into the mix
-
-### Changes since 10.1.5
-
-For a full overview you can also see the [10.1.6 milestone](https://github.com/akka/akka-http/milestone/44?closed=1):
-
-#### Improvements
-
-##### akka-http-core
-
- * Require Akka 2.5.19 for JDK 11 support
- * Move RoutingSettings to akka-http module ([#2307](https://github.com/akka/akka-http/issues/2307))
- * Use collision-resistant maps in header parsing ([#2276](https://github.com/akka/akka-http/issues/2276))
- * Depend on Scala 2.12.8 to allow Java usage from JDK 11 ([#2305](https://github.com/akka/akka-http/issues/2305))
- * Add application/merge-patch+json ([#2190](https://github.com/akka/akka-http/issues/2190))
- * Require Akka 2.5.10 and use the new version checker utility ([#1880](https://github.com/akka/akka-http/issues/1880))
- * Add HttpEntity.isStrict ([#2228](https://github.com/akka/akka-http/issues/2228))
- * Log time spent in a pool slot for simpler spotting of slow transition periods ([#2226](https://github.com/akka/akka-http/issues/2226))
- * Replace existing HTTP Status Code 425 with TOO_EARLY ([#2255](https://github.com/akka/akka-http/issues/2255))
- * Java API - call scala HttpEntity.toStrict that respects maxBytes ([#2287](https://github.com/akka/akka-http/issues/2287))
- * Override `getForKeyCaseInsensitive` in `HttpMethods` ([#2303](https://github.com/akka/akka-http/issues/2303))
- * Fix several warnings across all the modules ([#2292](https://github.com/akka/akka-http/issues/2292))
- * Deprecate unofficial Microsoft media-types and add the official ones ([#2264](https://github.com/akka/akka-http/issues/2264))
-
-##### akka-http
-
- * Use collision-resistant maps for formFieldMaps ([#2274](https://github.com/akka/akka-http/issues/2274))
- * Add Directive#tcollect and Directive1#collect ([#2253](https://github.com/akka/akka-http/issues/2253))
- * Do not set dispatcher for file directives and remove file-io-dispatcher config ([#1879](https://github.com/akka/akka-http/issues/1879))
- * Add new method for routes chaining in Java DSL ([#1170](https://github.com/akka/akka-http/issues/1170))
- * Fail with unwrapped exception when using CompletionStage ([#2054](https://github.com/akka/akka-http/issues/2054))
- * Return RequestEntityTooLarge status code in case of EntityStreamSizeException ([#2279](https://github.com/akka/akka-http/issues/2279))
-
-##### akka-http-testkit
- * `akka-stream-testkit` is now a provided dependency for `akka-http-testkit` ([#2262](https://github.com/akka/akka-http/issues/2262))
-
-#### Bug Fixes
-
-##### akka-http-core
-
- * Client pool: exponential backoff after failed connection attempts ([#1391](https://github.com/akka/akka-http/issues/1391))
- * Fix broken multi-byte UTF-8 decoding in HeaderParser if UTF-8 sequence is cut in the middle ([#1484](https://github.com/akka/akka-http/issues/1484))
- * Fix limiting of chunk size in the NoCode encoder ([#2252](https://github.com/akka/akka-http/issues/2252))
- * Allow chunked responses in HttpMessage with protocol = HTTP/2, fixes ([#2217](https://github.com/akka/akka-http/issues/2217))
-
-##### akka-http
-
- * Default exception handlers do now discard entity bytes when completing a request that ended in error ([#2084](https://github.com/akka/akka-http/issues/2084))
- * Fix cancellation and head-of-line blocking in fileUpload directive ([#2224](https://github.com/akka/akka-http/issues/2224))
- * toStrict the entity when parsing multiple form fields ([#2283](https://github.com/akka/akka-http/issues/2283))
- * Fix CsvSeq unmarshaller to include trailing empty string values in the result `Seq[T]` ([#2249](https://github.com/akka/akka-http/issues/2249))
-
-##### akka-http2-support
-
- * Handle stream cancellation while outgoing data is buffered ([#2237](https://github.com/akka/akka-http/issues/2237))
-
-##### akka-http-caching
-
- * Fix that LfuCache ttl can be equal to tti ([#2188](https://github.com/akka/akka-http/issues/2188))
-
-## 10.1.5
-
-10.1.5 is the sixth release in the 10.1.x series of Akka HTTP.
-
-It is mainly a mitigation for the [DoS vulnerability when using `decodeRequest`](https://akka.io/blog/news/2018/08/30/akka-http-dos-vulnerability-found)
-
-### Migration Notes
-
-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 `decodeRequest` to 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 `HttpEntity.toStrict` or the `toStrictEntity` directive (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.
-
-### **Changes since 10.1.4**
-
-For a full overview you can also see the [10.1.5 milestone](https://github.com/akka/akka-http/milestone/43?closed=1):
-
- * Restrict the maximum size of a request entity after uncompressing it with `decodeRequest` [#2137](https://github.com/akka/akka-http/issues/2137)
- * Restrict the maximum size of a request entity when reading it into memory with `toStrict` [#2186](https://github.com/akka/akka-http/pull/2186)
- * Correctly set a default `parallelism` value when none is specified for HTTP/2 [#2165](https://github.com/akka/akka-http/pull/2165)
- * Avoid matching an empty pattern when using `PathMatcher.repeat` [#2097](https://github.com/akka/akka-http/issues/2097)
- * Add `ServerSentEvent.heartbeat()` to the Java DSL [#2187](https://github.com/akka/akka-http/issues/2187)
-
-## 10.1.4
-
-10.1.4 is the fifth release in the 10.1.x series of Akka HTTP.
-
-Among many other things, this release includes a fix for handling early responses in the client, HTTP/2 improvements and many updates to the documentation.
-
-### **Changes since 10.1.3**
-
-For a full overview you can also see the [10.1.4 milestone](https://github.com/akka/akka-http/milestone/42?closed=1):
-
-#### Fixes in akka-http-core
-
- * Support for scheme ending in digit in Uri.from ([#2080](https://github.com/akka/akka-http/issues/2080))
- * Allow `MediaType`s in `Set`s ([#2144](https://github.com/akka/akka-http/issues/2144))
- * Allow creating an unencrypted HTTP/2 server from Java ([#2110](https://github.com/akka/akka-http/issues/2110))
- * Fix a bug in handling chunked responses in the new connection pool ([#2138](https://github.com/akka/akka-http/issues/2138))
- * As a websocket client, support receiving the upgrade request in parts ([#2152](https://github.com/akka/akka-http/pull/2152))
- * Support HSTS headers with trailing semicolons and unusual field ordering ([#2122](https://github.com/akka/akka-http/issues/2122))
-
-#### Improvements in akka-http-core
-
- * Improved graceful shutdown behavior ([#2090](https://github.com/akka/akka-http/issues/2090))
- * More sensible default for bindAndHandleAsync parallelism setting with HTTP/2 ([#2145](https://github.com/akka/akka-http/issues/2145))
-
-#### Improvements in akka-http
-
- * Allow java/scala conversion for Routes for users ([#891](https://github.com/akka/akka-http/issues/891))
- * Commonize marshalling selection code ([#2004](https://github.com/akka/akka-http/pull/2004))
-
-#### Improvements in akka-http-testkit
-
- * Allow configuring the marshalling timeout ([#2127](https://github.com/akka/akka-http/issues/2127))
-
-#### Improvements in docs
-
- * Fix broken links at release notes ([#2082](https://github.com/akka/akka-http/pull/2082))
- * Fix links to RequestEntityExpectedRejection api documentation ([#2094](https://github.com/akka/akka-http/pull/2094))
- * Document GenericMarshallers.futureMarshaller ([#2095](https://github.com/akka/akka-http/pull/2095))
- * Clarify not all abrupt client go-aways are clean ([#2101](https://github.com/akka/akka-http/pull/2101))
- * Clarify documentation for PathDirectives ([#2109](https://github.com/akka/akka-http/pull/2109))
- * Updated outdated SecurityDirectives documentation ([#1715](https://github.com/akka/akka-http/issues/1715))
- * Link to the Play and Lagom websites ([#2121](https://github.com/akka/akka-http/pull/2121))
- * Improve source-streaming docs ([#2131](https://github.com/akka/akka-http/pull/2131))
- * Add warning banner when browsing old versions ([#2135](https://github.com/akka/akka-http/issues/2135))
-
-## 10.1.3
-
-10.1.3 is the fourth release in the 10.1.x series of Akka HTTP.
-
-This release addresses a critical memory leak issue introduced by the graceful termination infrastructure added in 10.1.2.
-No other risky changes are made in this release, in order to make it a trustworthy fix drop-in replacement of 10.1.2.
-
-### **Changes since 10.1.2**
-
-For a full overview you can also see the [10.1.3 milestone]( https://github.com/akka/akka-http/milestone/41?closed=1):
-
-#### Fixes in akka-http-core
-
- * ServerTerminator memory leak in 10.1.2 ([#2067](https://github.com/akka/akka-http/issues/2067))
- * Avoid eagerly failing connections when request closes ([#2066](https://github.com/akka/akka-http/issues/2066))
-
-#### Fixes in docs
-
- * Correct pipelining-limit flag name ([#2059](https://github.com/akka/akka-http/issues/2059))
- * Fix link to compatibility rules section ([#2062](https://github.com/akka/akka-http/issues/2062))
-
-#### Improvements in docs
-
- * Reference documentation for Graceful Termination ([#2072](https://github.com/akka/akka-http/issues/2072))
- * Enhance Caching Documentation ([#2060](https://github.com/akka/akka-http/issues/2060))
-
-## 10.1.2
-
-10.1.2 is the third release in the 10.1.x series of Akka HTTP.
-
-Notably, this release:
-
- * Introduces "Graceful" Server Termination ([#118](https://github.com/akka/akka-http/issues/118)): calling the newly introduced `terminate` on the `ServerBinding` will cause the binding to start gracefully rejecting new requests, while giving existing requests a deadline to complete normally.
- * Discards Entities in Default RejectionHandler ([#38](https://github.com/akka/akka-http/issues/38)). Previously, when rejecting a request, the default rejection handler would not consume the request entity. The default rejection handlers have been updated to consume the request in this case.
- * Appends a newline to every element when streaming CSV (and NDJSON, [#1931](https://github.com/akka/akka-http/issues/1931)): Previously, CSV lines would only be interspersed with newlines, but no final newline would be sent. While arguably this was a bug in itself, it also had the unfortunate effect that a newline would only be emitted when the next CSV line became available, which is especially surprising in situations where CSV data is produced relatively slowly.
-
-### **Changes since 10.1.1**
-
-For a full overview you can also see the [10.1.2 milestone](https://github.com/akka/akka-http/milestone/40?closed=1):
-
-#### Fixes in akka-http-core
-
- * Default rejection handlers do now discard entity bytes when rejecting a request ([#38](https://github.com/akka/akka-http/issues/38))
-
-#### Improvements in akka-http-core
-
- * Added toStrict to WS Messages ([#15](https://github.com/akka/akka-http/issues/15))
- * Accept LF end of line instead of CRLF only ([#106](https://github.com/akka/akka-http/issues/106))
- * Add setting ignore-illegal-header-for ([#687](https://github.com/akka/akka-http/issues/687))
- * Support parameters for custom media types ([#2005](https://github.com/akka/akka-http/issues/2005))
- * Accept response before request has been sent completely ([#1746](https://github.com/akka/akka-http/issues/1746))
- * Added ability to set https proxy host and port through application.conf ([#995](https://github.com/akka/akka-http/issues/995))
- * "Graceful" Server Termination #188 ([#2035](https://github.com/akka/akka-http/issues/2035))
-
-#### Fixes in akka-http
-
- * fix 500 error in conditional GET for non-etag response ([#1951](https://github.com/akka/akka-http/issues/1951))
-
-#### Improvements in akka-http
-
- * Discard Entity in Default RejectionHandler ([#38](https://github.com/akka/akka-http/issues/38))
- * Adds missing parameter with required value directive for Java API ([#2025](https://github.com/akka/akka-http/issues/2025))
- * Add Java DSL optionMarshaller ([#1247](https://github.com/akka/akka-http/issues/1247))
- * Append newline to every element when streaming CSV (and NDJSON). ([#1931](https://github.com/akka/akka-http/issues/1931))
-
-#### Fixes in docs
-
- * Fix Java snippet in Path Matcher doc page ([#2000](https://github.com/akka/akka-http/issues/2000))
- * Add missing methods for creating custom binary MediaTypes ([#2008](https://github.com/akka/akka-http/issues/2008))
- * Update outdated link in "Handling blocking operations" ([#2038](https://github.com/akka/akka-http/issues/2038))
-
-#### Improvements in docs
-
- * Added explanations for beginners how to access the server ([#1975](https://github.com/akka/akka-http/issues/1975))
- * Add dynamically updating routes example ([#1935](https://github.com/akka/akka-http/issues/1935))
- * Recommend static Directives. imports over AllDirectives ([#1993](https://github.com/akka/akka-http/issues/1993))
-
-#### Fixes in akka-http2-support
-
- * Ignore unknown h2 SETTINGS ([#2039](https://github.com/akka/akka-http/issues/2039))
- * Allow h2 SETTINGS with large max header table size ([#2040](https://github.com/akka/akka-http/issues/2040))
-
-#### Improvements in akka-http2-support
-
- * Run h2spec integration tests ([#1988](https://github.com/akka/akka-http/issues/1988))
- * Allow Http2 without negotiation/TLS ([#1934](https://github.com/akka/akka-http/issues/1934))
-
-## 10.1.1
-
-See the [announcement](https://akka.io/blog/news/2018/03/27/akka-http-10.1.1-released.html) and
-closed tickets on the [10.1.1 milestone](https://github.com/akka/akka-http/milestone/36?closed=1).
-
-10.1.1 is the second release in the 10.1.x series of Akka HTTP.
-
-
-This release brings a number of small, yet long requested features, including:
-
- * automatic WebSocket keep-alive using `Ping` frames,
- * removing the need for implicit parameters in order to call `Route.seal` (in Scala DSL)
-
-As usual, the release is backwards compatible as outlined in our [binary compatibility guidelines](https://doc.akka.io/docs/akka-http/current/compatibility-guidelines.html).
-
-### **List of changes (since 10.1.0)**
-
-#### Fixes in akka-http-core
-
- * Emit entity truncation errors before completing graph stage ([#1947](https://github.com/akka/akka-http/issues/1947))
- * Fix type parameters in Java API to work with latest Akka ([#1965](https://github.com/akka/akka-http/issues/1965))
-
-#### Improvements in akka-http-core
-
- * Transparent websocket ping/pong (keep alive) ([#1938](https://github.com/akka/akka-http/issues/1938))
- * Fix a few Scala 2.13.0-M3 compilation issues ([#1918](https://github.com/akka/akka-http/issues/1918))
- * Always parse Content-Encoding and WebSocket headers ([#1937](https://github.com/akka/akka-http/issues/1937))
- * Support conversion between scaladsl.Uri and javadsl.Uri ([#1950](https://github.com/akka/akka-http/issues/1950))
-
-#### Improvements in akka-http
-
- * Remove not needed implicits from Route.seal ([#1928](https://github.com/akka/akka-http/issues/1928))
-
-#### Improvements in akka-http-testkit
-
- * Fix type parameter variance in Java API to work with latest Akka ([#1965](https://github.com/akka/akka-http/issues/1965))
-
-#### Improvements in documentation
-
- * Document client-side for streaming JSON ([#1964](https://github.com/akka/akka-http/issues/1964))
- * Add package name to `PathMatcher` javadsl docs ([#1933](https://github.com/akka/akka-http/issues/1933))
- * Fix paradox error for discard entity bytes ([#1944](https://github.com/akka/akka-http/issues/1944))
- * Minor correction in rejections.md ([#1924](https://github.com/akka/akka-http/issues/1924))
- * Cache docs: more explicit imports, create cache once ([#1955](https://github.com/akka/akka-http/issues/1955))
- * Better caching example for Java
-
-#### Infrastructure and build fixes
-
- * Fully remove OSGi support ([#1943](https://github.com/akka/akka-http/issues/1943))
- * Which was already removed and discussed in 10.1.0
-
-
-
-## 10.1.0
-
-See the [announcement](https://akka.io/blog/news/2018/03/08/akka-http-10.1.0-released.html) and
-closed tickets on the [10.1.0 milestone](https://github.com/akka/akka-http/milestone/35?closed=1).
-
-10.1.0 is the first release in the 10.1.x series of Akka HTTP.
-
-The most important changes are:
-
- * Removing support for Akka 2.4.x which is at its end-of-life with the end of 2017. In the future, this will allow us
- to make use of features that only Akka 2.5 supports.
- * Removing methods that have been deprecated during the life-time of Akka HTTP 10.0.x. For now, methods only deprecated
- in the last release of Akka HTTP, 10.0.11, are not yet removed to allow for a smooth transition.
- * The new client pool implementation introduced in 10.0.11 is now the default. We have identified and fixed several
- bugs in the RC period so by now we are quite confident that the new client pool will be a solid replacement for the
- legacy one.
- * Documentation has been completely consolidated between Scala and Java pages. Hundreds of directive
- documentation pages have been merged in a tireless effort by [@jonas](https://github.com/jonas),
- [@jlprat](https://github.com/jlprat), and Akka team's [@raboof](https://github.com/raboof).
-
-### Akka is not an explicit dependency anymore / Removal of Akka 2.4 support
-
-Akka HTTP 10.0.x has always supported Akka 2.5, while allowing users to still remain on Akka 2.4.x if they choose to do so.
-By now Akka 2.4 has reached its end of life. Therefore, Akka HTTP 10.1.x only supports Akka >= 2.5.11
-(and future versions during the life of Akka HTTP 10.1.x) so we will be able to make of features only provided by Akka 2.5.
-In some cases we bump the minimum supported patch version of Akka to be able to use new features quickly.
-
-Using Akka HTTP with Akka 2.5 used to be
-a bit confusing, because Akka HTTP explicitly depended on Akka 2.4. Trying to use it together with Akka 2.5,
-running an Akka HTTP application could fail with class loading issues if you forgot to add a dependency to
-both `akka-actor` *and* `akka-stream` of the same version. For that reason, we changed the policy not to depend on `akka-stream`
-explicitly anymore but mark it as a `provided` dependency in our build. That means that you will *always* have to add
-a manual dependency to `akka-stream`. Please make sure you have chosen and added a dependency to `akka-stream` when
-updating to the new version (veterans may remember this policy from Spray).
-
-### Deprecation Removals
-
-Methods were removed that have been deprecated during the life-time of Akka HTTP 10.0.x. Methods that were only deprecated
-in the last release of Akka HTTP, 10.0.11, are not yet removed to allow for a smooth transition. In general, our guarantee
-for minor release updates is that code that compiled on the latest version of the previous minor release (10.0.11 in this case)
-should be both source and binary compatible with the latest version of the current minor release. We might make
-exceptions to the rule for cases where the maintenance burden seems greater than the risk of breaking major users / third-party
-libraries. We'll treat any other binary incompatibilities as regressions.
-
-### New client pool implementation is now the default
-
-The new client pool implementation introduced in 10.0.11 is now the default. Since 10.0.11, we fixed several bugs in the
-new client pool implementation.
-You can still fall back to the old implementation by setting `akka.http.host-connection-pool.pool-implementation = legacy`.
-
-### Compatibility Notes
-
-As the @ref[compatibility notes](../compatibility-guidelines.md) explain in detail, we guarantee binary compatibility. In
-some cases, however, a new version is not strictly source compatible. We try to limit the impact of these kinds
-of changes but sometimes, they are inevitable to improve the API.
-
-Source incompatible changes are:
-
- * Removed deprecated methods from 10.0.x
- * `ServerBinding.unbind` return type has been changed to @scala[`Future[Done]`]@java[`CompletionStage[Done]`] for
- consistency.
-
-### Support for Scala 2.13.0-M3
-
-Akka HTTP 10.1.0 is released for Scala 2.11, 2.12, and 2.13.0-M3. Due to a [regression in Scala 2.13.0-M3](https://github.com/scala/scala-dev/issues/467)
-tail call optimization does not apply anymore in some cases where it did before which might lead to stack overflow when
-running with Scala 2.13.0-M3.
-
-
-### Removal of OSGi support
-
-Supporting OSGi is error prone and high maintenance and it repeatably broke, blocked releases, or metadata turned out to
-be wrong. As we are no experts in OSGi, and are nowadays focusing our efforts on JDK9+ jigsaw compatibility
-we had to remove OSGi support for now. If you care about OSGi support please step up and help out. Most important
-would be adding tests that verify that the OSGi infrastructure does not break the build and the metadata actually works
-at runtime. See [#1852](https://github.com/akka/akka-http/issues/1852) for more information.
-
-### List of changes (since 10.1.0-RC2)
-
-#### Improvements
-
-##### akka-http-core
-
- * Add headers and getHeaders method to HttpMessage ([#1731](https://github.com/akka/akka-http/issues/1731))
- * More specific warning for HTTPS requests on HTTP endpoints ([#1829](https://github.com/akka/akka-http/issues/1829))
- * Add ability to access current response timeout ([#1811](https://github.com/akka/akka-http/issues/1811)) ([#1828](https://github.com/akka/akka-http/issues/1828))
- * Move ClientTransport from ConnectionPoolSettings to ClientConnectionSettings so the transport can be configured in all client APIs ([#1562](https://github.com/akka/akka-http/issues/1562))
-
-##### akka-http
-
- * Support OAuth2 access token in URI query component as defined in RFC6750 ([#1769](https://github.com/akka/akka-http/issues/1769))
-
-##### akka-http2-support
-
- * Support for trailing response headers in HTTP/2 ([#1857](https://github.com/akka/akka-http/issues/1857))
-
-##### Documentation
-
- * Add docs and tests for combining | with / in paths ([#1861](https://github.com/akka/akka-http/issues/1861))
- * Fix links to objects in the API docs
-
-#### Bug Fixes
-
-##### akka-http-core
-
- * Normalize port in `Uri.apply` consistently ([#1763](https://github.com/akka/akka-http/issues/1763))
- * Return status 400 instead of 500 for requests with invalid URI scheme ([#36](https://github.com/akka/akka-http/issues/36))
- * Allow Sec-WebSocket-Extensions in requests
- * Fix incompatibility of Akka HTTP with Akka typed ([#1878](https://github.com/akka/akka-http/issues/1878))
-
-##### akka-http2-support
-
- * Fix HTTP/2 trying to send even if stream window was depleted ([#1882](https://github.com/akka/akka-http/issues/1882))
-
-## 10.1.0-RC2
-
-See the [announcement](https://akka.io/blog/news/2018/02/12/akka-http-10.1.0-RC2-released.html) and
-closed tickets on the [10.1.0-RC2 milestone](https://github.com/akka/akka-http/milestone/34?closed=1).
-
-10.1.0-RC2 is the second release candidate for the upcoming Akka HTTP 10.1.0. We focused on stabilizing the new
-client connection pool. Over the last month our test suite caught lots of edge cases that were fixed for this release.
-Also, we improved logging output for the new pool.
-
-### List of changes (since 10.1.0-RC1)
-
-#### Improvements
-
-##### akka-http-core
-
- * Add HTTP status code `421` ([#1749](https://github.com/akka/akka-http/issues/1749))
- * Add HTTP status code `103` ([#1803](https://github.com/akka/akka-http/issues/1803))
- * Add `Uri.Path` `?/` operator #1793 ([#1794](https://github.com/akka/akka-http/issues/1794))
- * Add `UserAgent` header parse Java Api ([#1807](https://github.com/akka/akka-http/issues/1807))
- * Optimization: Avoid creation of async callback per request in RequestTimeoutStage ([#1848](https://github.com/akka/akka-http/issues/1848))
- * Add `application/grpc+proto` content type / media type ([#1844](https://github.com/akka/akka-http/issues/1844))
- * LogByteStringTools now logs errors on debug log (it's a debug feature after all) ([#1780](https://github.com/akka/akka-http/issues/1780))
- * Suggest valid max-open-requests values on config error ([#1806](https://github.com/akka/akka-http/issues/1806))
- * Log the timed out request on server ([#1813](https://github.com/akka/akka-http/issues/1813))
- * Be more lenient to allow trailing whitespace after chunk size ([#1812](https://github.com/akka/akka-http/issues/1812))
- * In `Http().serverLayer` use `delayCancellation` to make behavior consistent with other server entry points ([#1822](https://github.com/akka/akka-http/issues/1822))
- * Add `HttpMessage.withProtocol` overload to return Scala type ([#1730](https://github.com/akka/akka-http/issues/1730))
-
-##### akka-http2-support
-
- * Add `Tls-session-info` header for http/2 ([#1432](https://github.com/akka/akka-http/issues/1432))
-
-##### akka-http
-
- * Add Java onSuccess overload to take a strict value ([#1821](https://github.com/akka/akka-http/issues/1821))
-
-##### Infrastructure
-
- * Lots of small documentation fixes
- * Use sbt-header to manage copyright headers
- * Introduce `WithLogCapturing` trait for suppressing log output for successful tests which allows more aggressive
- logging by default (which will be shown only for failures)
- * Fix search on documentation pages to return only one version of each page
- * Disable parallel testing on Jenkins to reduce spurious failures
-
-#### Bug Fixes
-
-##### akka-http-core
-
- * New client pool: Fix double registration for dispatch ([#1726](https://github.com/akka/akka-http/issues/1726))
- * New client pool: Automatically close connection when slot state -> Unconnected ([#1724](https://github.com/akka/akka-http/issues/1724))
- * New client pool: Make sure that failed and retryable requests are re-dispatched immediately ([#1735](https://github.com/akka/akka-http/issues/1735))
- * New client pool: Ignore "request entity completed" in state WaitingForResponseDispatch ([#1774](https://github.com/akka/akka-http/issues/1774))
- * New client pool: After slot failures remove slot from response dispatching queue ([#1775](https://github.com/akka/akka-http/issues/1775))
- * New client pool: Log retried request info ([#1781](https://github.com/akka/akka-http/issues/1781))
- * Parse and render token correctly for HttpChallenge and GenericHttpCredentials ([#1353](https://github.com/akka/akka-http/issues/1353))
- * Fix utf16 surrogate pair decoding in utf8 encoder ([#1760](https://github.com/akka/akka-http/issues/1760))
- * Use `431` status code when header exceeds max length for name or value ([#1800](https://github.com/akka/akka-http/issues/1800))
- * Fix customMediaTypes disabling predefined media type parsing ([#1786](https://github.com/akka/akka-http/issues/1786))
- * TLS should close connection when instructed by stream completion ([#380](https://github.com/akka/akka-http/issues/380))
-
-## 10.1.0-RC1
-
-See the [announcement](https://akka.io/blog/news/2017/12/22/akka-http-10.1.0-RC1-released.html) and
-closed tickets on the [10.1.0-RC1 milestone](https://github.com/akka/akka-http/milestone/26?closed=1).
-
-10.1.0-RC1 is the first release candidate for the next minor version of Akka HTTP. The most important changes are
-
- * Removing support for Akka 2.4.x which is at its end-of-life with the end of 2017. In the future, this will allow us
- to make use of features that only Akka 2.5 supports.
- * Removing methods that have been deprecated during the life-time of Akka HTTP 10.0.x. For now, methods only deprecated
- in the last release of Akka HTTP, 10.0.11, are not yet removed to allow for a smooth transition.
- * The new client pool implementation introduced in 10.0.11 is now the default. Please try it out and provide feedback
- during the RC period of this release so we can iron out any problems we may have missed initially.
- * Documentation has now almost completely been consolidated between Scala and Java pages. Hundreds of directive
- documentation pages have been merged in a tireless effort by [@jonas](https://github.com/jonas),
- [@jlprat](https://github.com/jlprat), and Akka team's [@raboof](https://github.com/raboof).
-
-### List of changes (since 10.0.11)
-
-#### Improvements
-
-##### akka-http-core
-
- * Add missing javadsl model bits and pieces ([#1679](https://github.com/akka/akka-http/issues/1679))
- * New client pool is now the default
- * Several improvements and fixes to new client pool implementation
- * Methods deprecated before (but not including) 10.0.11 were removed
- * Add convenience Java DSL `Http.cachedHostConnectionPoolHttps` ([#1644](https://github.com/akka/akka-http/issues/1644))
- * Add Retry-After header model ([#1554](https://github.com/akka/akka-http/issues/1554))
- * Adding percent encoding length check for Path.Uri ([#1553](https://github.com/akka/akka-http/issues/1553))
-
-##### akka-http
-
- * Methods deprecated before (but not including) 10.0.11 were removed
-
-#### akka-http-caching
-
- * Add non-lambda-capturing getOrLoad method to Cache ([#1536](https://github.com/akka/akka-http/issues/1536))
-
-#### Documentation
-
- * Almost the complete directive documentation has now been consolidated between Java and Scala. More than hundred
- pages have been simplified like this.
- * The top-level documentation structure has been clarified.
-
-#### Bug Fixes
-
-##### akka-http-core
-
- * Fix return type for `withStatus` methods to return proper scaladsl types ([#1623](https://github.com/akka/akka-http/issues/1623))
- * Fix "Cannot push port ... twice" in NewHostConnectionPool ([#1610](https://github.com/akka/akka-http/issues/1610)) and several other fixes
-
-##### Documentation
-
- * Fix generation/publication of javadoc (10.0.11 javadoc link pointed to scaladoc instead)
diff --git a/docs/src/main/paradox/release-notes/10.2.x.md b/docs/src/main/paradox/release-notes/10.2.x.md
deleted file mode 100644
index baf85efb8..000000000
--- a/docs/src/main/paradox/release-notes/10.2.x.md
+++ /dev/null
@@ -1,721 +0,0 @@
-# 10.2.x Release Notes
-
-## 10.2.10
-
-This release contains small improvements and bug fixes.
-
-### Changes since 10.2.9
-
-#### akka-http-core
-
-* Avoid loop in JavaQuery.render(HttpCharset, CharPredicate) [#4078](https://github.com/akka/akka-http/pull/4078)
-* Optimization: avoid array copy for string entities [#4098](https://github.com/akka/akka-http/pull/4098)
-* Allow zero max-content-length [#3903](https://github.com/akka/akka-http/pull/3903)
-* Move pool buffer into PoolInterface and fix pool sizing[#4132](https://github.com/akka/akka-http/pull/4132)
-* Use LIFO ordering in retry buffer of connection pool [#4133](https://github.com/akka/akka-http/pull/4133)
-* Fix for Uri.collapseDotSegments failing on some relative paths [#2507](https://github.com/akka/akka-http/pull/2507)
-* HTTP/2: When connection is aborted due to completion timeout, abort ongoing substreams (on Akka 2.6) [#4062](https://github.com/akka/akka-http/pull/4062)
-* HTTP/2: Add client-side cancellation propagation delay [#4027](https://github.com/akka/akka-http/pull/4027)
-* HTTP/2: Defer enqueing out streams when state machine is already running [#4088](https://github.com/akka/akka-http/pull/4088)
-
-#### akka-http
-
-* Allow custom verifier in Credentials.Provided [#4146](https://github.com/akka/akka-http/pull/4146)
-* Make `toStrictEntity` fail with bad request in case of entity errors [#4135](https://github.com/akka/akka-http/pull/4135)
-
-#### docs
-
-* Replace abandoned swakka with actively maintained swagger-akka-http [#4129](https://github.com/akka/akka-http/pull/4129)
-
-#### akka-http-caching
-
-* Avoid locking cache during directive processing [#4093](https://github.com/akka/akka-http/pull/4093)
-* Fix cached execution and test [#4099](https://github.com/akka/akka-http/pull/4099)
-
-## 10.2.9
-
-This release is a bugfix release fixing a few regressions introduced with 10.2.8:
-
- * Avoid memory leak when HTTP/2 is enabled ([#4047](https://github.com/akka/akka-http/pull/4047))
- * Revert the default behavior for ServerSentEvent parsing back to the 10.2.7 default. Empty events are now silently skipped
- again to keep compatibility with existing (akka-http) servers. If you want to interpret empty events, you can now turn
- on `akka.http.sse.emit-empty-events` ([#4043](https://github.com/akka/akka-http/pull/4043))
- * Restore compatibility with existing Lightbend Telemetry versions [#4055](https://github.com/akka/akka-http/pull/4055)
-
-### Changes since 10.2.8
-
-#### akka-http-core
-
-* Hide empty SSE events behind flag [#4043](https://github.com/akka/akka-http/pull/4043)
-* Unregister connection from MasterTermination when done [#4047](https://github.com/akka/akka-http/pull/4047)
-* Revert part of "core: cleanup some unused vals (#4033)" [#4055](https://github.com/akka/akka-http/pull/4055)
-* Silence noisy error when HTTP/2 connection is closed with idle-timeout [#4044](https://github.com/akka/akka-http/pull/4044)
-
-## 10.2.8
-
-This release is a maintenance release, mostly fixing a few smaller issues around HTTP/2 support.
-
-Akka HTTP now also supports graceful termination for HTTP/2 servers. If coordinated shutdown is enabled for a server binding
-via `ServerBinding.addToCoordinatedShutdown`, the server will allow ongoing requests to be completed for a configurable
-period of time while immediately rejecting incoming requests before shutting down the application process.
-This helps to avoid downtime during rolling upgrades.
-
-#### akka-http-core
-
-* Enable idle-timeout when http2 is enabled [#3965](https://github.com/akka/akka-http/pull/3965)
-* Fix h2c via Upgrade [#4000](https://github.com/akka/akka-http/pull/4000)
-* Fail pool slot if connection is canceled before it is failed [#3981](https://github.com/akka/akka-http/pull/3981)
-* Ensure PoolMaster.shutdown(…) does not hang [#4004](https://github.com/akka/akka-http/pull/4004)
-* Implement graceful termination for HTTP/2 servers [#4018](https://github.com/akka/akka-http/pull/4018)
-* Remove unused var from ServerTerminator [#4011](https://github.com/akka/akka-http/pull/4011)
-
-#### akka-http
-
-* Interpret SSE heartbeats as events [#4020](https://github.com/akka/akka-http/pull/4020)
-
-#### docs
-
-* Simplify bullet points in 10.2.7 release notes [#3926](https://github.com/akka/akka-http/pull/3926)
-* Backport release notes from 10.1 [#3953](https://github.com/akka/akka-http/pull/3953)
-* Replace deprecated functions in Routing DSL docs [#3966](https://github.com/akka/akka-http/pull/3966)
-* Fix the documentation for RejectionHandler [#4013](https://github.com/akka/akka-http/pull/4013)
-
-#### build
-
-* Dependency updates
-* Rename branch master -> main [#3911](https://github.com/akka/akka-http/pull/3911)
-* Hide test jar with complicated name from scala-steward [#3980](https://github.com/akka/akka-http/pull/3980)
-* Use fuzzy `+~` to switch Scala versions [#3970](https://github.com/akka/akka-http/pull/3970)
-
-## 10.2.7
-
-This release is an important security fix release.
-
-Most importantly, we fixed a problem with parsing headers containing `comment` elements ([#3918](https://github.com/akka/akka-http/issues/3918)). The HTTP spec allows arbitrary
-nesting of those elements, e.g. in the `User-Agent` header. When such a header is parsed, an Akka HTTP application may
-fail fatally with a `StackOverflowError`. Akka HTTP 10.2.7 mitigates this issue by conservatively limiting the allowed
-depth of `comment` elements in headers. See @ref[the advisory for CVE-2021-42697](../security/2021-CVE-2021-42697-stack-overflow-parsing-user-agent.md) for more information about this security issue.
-
-Another issue has been fixed in relation to header rendering ([#3717](https://github.com/akka/akka-http/issues/3717)).
-Akka HTTP does not validate that header values (or keys)
-are well-formed when those are provided as Strings (e.g. in a `RawHeader`). In particular, HTTP headers are not allowed
-to contain the special characters `'\r'` or `'\n'` which are used to delineate headers in an HTTP message. Before 10.2.7,
-Akka HTTP would naively render those broken header values leading to broken HTTP messages. The generation of headers is
-usually in complete control of the application. However, an application may accidentally pass incoming unvalidated user
-data to response headers. In such a case, a remote user might be able to inject line terminators into the response headers
-leading to invalid or misleading HTTP response messages. Depending on the server setup, this can be a building block for
-severe attacks.
-
-To mitigate this issue, Akka HTTP now discards outgoing headers containing line terminators and logs a warning. Users
-are encouraged to be on the watch when creating headers (or any kind of outgoing data) from unvalidated user input as this
-is a common vector for different kinds of attacks.
-
-
-### Changes since 10.2.6
-
-#### akka-http-core
-
-* Limit comment nesting in header parser[#3924](https://github.com/akka/akka-http/pull/3924)
-* Discard outgoing headers containing line breaks [#3922](https://github.com/akka/akka-http/pull/3922)
-* Avoid calling numConnectedSlots when possible [#3904](https://github.com/akka/akka-http/pull/3904)
-* Simplify HeaderCompression [#3871](https://github.com/akka/akka-http/pull/3871)
-* End HTTP/2 stream with empty DATA rather than empty HEADERS [#3913](https://github.com/akka/akka-http/pull/3913)
-
-## 10.2.6
-
-This release is a bug fix release that fixes a bug in HTTP/2 processing, [#3890](https://github.com/akka/akka-http/issues/3890).
-
-## 10.2.5
-
-This release includes a set of performance improvements in the HTTP/2 infrastructure. Aside from internal improvements,
-some performance-related changes introduce new APIs or settings:
-
-#### HTTP/2: Trailers on messages with Strict entities
-
-HTTP/2 server and client can now send `Strict` entities to completely avoid stream materialization overhead for common
-use cases that require no streaming. This required providing a new way to attach trailing headers to a message also for
-messages with `Strict` entities. For that purpose the new attribute `AttributeKeys.trailer` of type @apidoc[Trailer] can be
-attached to a message. This is a common scenario for gRPC which uses trailing headers to transmit the status code in a response.
-
-Streaming entities using `Chunked` entities can still use the `LastChunk` to provide trailing headers.
-
-See @ref[Trailing Headers](../server-side/http2.md#trailing-headers) for more information.
-
-#### HTTP/2: Collect Strict entities
-
-HTTP/2 servers can request to produce `Strict` entities also for incoming requests by using the new
-`akka.http.server.http2.min-collect-strict-entity-size` setting. With that setting, the server can be instructed to
-hold back an incoming request to collect more data until either the request has been fully received (`Strict` entity is
-dispatched) or the given limit of collected data has been reached (`Chunked` entity is dispatched as before).
-This is another optimization to avoid stream materialization overhead where possible for small requests (also common with
-simple gRPC requests).
-
-The setting is still disabled by default. See the accompanying comments in the @ref[reference.conf](../configuration.md#configuration)
-for more information.
-
-#### Other notable improvements
-
- * Client connection pool has a new `keep-alive-timeout` to avoid race conditions with server-side timeouts.
- See @ref[Keep Alive Timeout](../common/timeouts.md#keep-alive-timeout).
-
-### Changes since 10.2.4
-
-#### akka-http-core
-
-##### Features
-
-* Add pool keep-alive-timeout [#3816](https://github.com/akka/akka-http/pull/3816)
-* Add flag to log WebSocket frame traffic [#3739](https://github.com/akka/akka-http/pull/3739)
-* Move `isStrict` up a level to ws.Message [#3847](https://github.com/akka/akka-http/pull/3847)
-* Add setting to automatically collect HTTP/2 request entity data into strict entities [#3829](https://github.com/akka/akka-http/pull/3829)
-* Allow trailing HTTP/2 headers on strict responses [#3820](https://github.com/akka/akka-http/pull/3820)
-
-##### Improvements / Fixes
-
-* Include port in HTTP/2 binding warning [#3793](https://github.com/akka/akka-http/pull/3793)
-* Don't send '100 Continue' if 'Content-Length' header is 0, doesn't exist or data got sent early [#3786](https://github.com/akka/akka-http/pull/3786)
-* Preserve original response headers during server termination [#3819](https://github.com/akka/akka-http/pull/3819)
-* Remove the requirement of max-open-requests being a power of two [#3827](https://github.com/akka/akka-http/pull/3827)
-* Add detail to onBadProtocol [#2877](https://github.com/akka/akka-http/pull/2877)
-* Back off on HTTP/2 client persistent connection failure [#3857](https://github.com/akka/akka-http/pull/3857)
-* Block demux stage completion until in-flight ops complete [#3734](https://github.com/akka/akka-http/pull/3734)
-* Ensure unhandled error ultimately get translated into GOAWAY frames [#3839](https://github.com/akka/akka-http/pull/3839)
-* Properly propagate completion through PersistentConnection [#3855](https://github.com/akka/akka-http/pull/3855)
-* Remove Http2FrameRendering stage [#3838](https://github.com/akka/akka-http/pull/3838)
-* Remove reflective access to alpn classes (JDK16 support) [#3811](https://github.com/akka/akka-http/pull/3811)
-
-##### Optimizations
-
-* Cache ContentType rendering [#3830](https://github.com/akka/akka-http/pull/3830)
-* Cache ModeledHeader.value [#3846](https://github.com/akka/akka-http/pull/3846)
-* Cache lowercaseName in `ModeledCustomHeaderCompanion` [#3851](https://github.com/akka/akka-http/pull/3851)
-* Only render date-header once per second [#3832](https://github.com/akka/akka-http/pull/3832)
-* Don't include RequestTimeoutSupport if disabled [#3862](https://github.com/akka/akka-http/pull/3862)
-* Fix UriParser constructor performance [#3813](https://github.com/akka/akka-http/pull/3813)
-* Increase some default buffer sizes [#3863](https://github.com/akka/akka-http/pull/3863)
-* A few simple microoptimizations that turned up in profiling [#3872](https://github.com/akka/akka-http/pull/3872)
-* Append new trailing headers at the end [#3821](https://github.com/akka/akka-http/pull/3821)
-* Avoid async boundary in ProtocolSwitch [#3831](https://github.com/akka/akka-http/pull/3831)
-* Avoid calling LoggingAdapter.isDebugEnabled in multiplexer [#3869](https://github.com/akka/akka-http/pull/3869)
-* Avoid creating GenericOutlet for every out element [#3848](https://github.com/akka/akka-http/pull/3848)
-* Avoid extra allocations in frame renderer [#3823](https://github.com/akka/akka-http/pull/3823)
-* Cache expensive `isDebugEnabled` call [#3850](https://github.com/akka/akka-http/pull/3850)
-* Convert stream handling map to LongMap [#3845](https://github.com/akka/akka-http/pull/3845)
-* Don't recordStateChange when debug logging is disabled [#3842](https://github.com/akka/akka-http/pull/3842)
-* Fix window management while CollectingIncomingData [#3837](https://github.com/akka/akka-http/pull/3837)
-* Provide missing handling logic in CollectingIncomingData state + tests [#3837](https://github.com/akka/akka-http/pull/3837)
-* Import shaded twitter hpack library (APL2) [#3849](https://github.com/akka/akka-http/pull/3849)
-* Never create Default entity [#3841](https://github.com/akka/akka-http/pull/3841)
-* Optimize header parsing by caching headers in HPACK tables [#3861](https://github.com/akka/akka-http/pull/3861)
-* Support Strict entities in Http2SubStream [#3824](https://github.com/akka/akka-http/pull/3824)
-* Use ByteString.length instead of ByteString.size [#3853](https://github.com/akka/akka-http/pull/3853)
-* Use cached ContentType.value instead of toString [#3865](https://github.com/akka/akka-http/pull/3865)
-* Use mutable.Queue for state in multiplexer [#3873](https://github.com/akka/akka-http/pull/3873)
-
-#### Build
-
-* Update caffeine from 2.8.8 to 2.9.0 [#3768](https://github.com/akka/akka-http/pull/3768)
-* Update github-api from 1.122 to 1.123 [#3777](https://github.com/akka/akka-http/pull/3777)
-* Update to Scala 2.13.5, 2.12.13 and scalafix 0.9.26 [#3780](https://github.com/akka/akka-http/pull/3780)
-* Finally update to sbt 1.4.7 [#3781](https://github.com/akka/akka-http/pull/3781)
-* Publish to sonatype directly [#3792](https://github.com/akka/akka-http/pull/3792)
-* Import shaded twitter hpack library (APL2) [#3849](https://github.com/akka/akka-http/pull/3849)
-* Update dependencies [#3870](https://github.com/akka/akka-http/pull/3870)
-* Disable parallel test execution during Github Actions runs [#3866](https://github.com/akka/akka-http/pull/3866)
-* Run full validation when workflow definition has changed [#3881](https://github.com/akka/akka-http/pull/3881)
-
-## 10.2.4
-
-This release fixes [CVE-2021-23339](https://nvd.nist.gov/vuln/detail/CVE-2021-23339), a vulnerability regarding interpretation of `Transfer-Encoding` headers. See
-@ref:[Incorrect Handling Of Transfer-Encoding Header](../security/2021-02-24-incorrect-handling-of-Transfer-Encoding-header.md).
-
-The vulnerability cannot be exploited using just Akka HTTP itself. Instead, Akka HTTP must be use as a proxy and the downstream server must be vulnerable itself, so
-that the proxy and the downstream server disagree on how to interpret a malformed request containing both `Transfer-Encoding` and `Content-Length` headers potentially
-leading to a "Request Smuggling" vulnerability. If you are using Akka HTTP as a reverse proxy, make sure to upgrade to the latest version.
-
-Starting from this version, only a single `Transfer-Encoding: chunked` header is allowed. HTTP/1.1 specifies other encodings, however, those are not supported or
-implemented in Akka HTTP. Formerly, Akka HTTP would just pass on unsupported `Transfer-Encoding` headers to the user which lead to the above security issue. Since
-Akka HTTP implements the "Transfer" part of the protocol, it seems reasonable to lock down allowed values for `Transfer-Encoding` to prevent security issues like this.
-Please let us know if this leads to compatibility problems with your software.
-
-The release contains one other notable change:
-
- * New option for handling conflicting Content-Type headers [#3727](https://github.com/akka/akka-http/pull/3727)
-
-## 10.2.3
-
-This release includes a working preview HTTP/2 client. Please consider using this preview to provide early feedback in case you find issues in your use-case. The HTTP/2 client will soon be included as an opt-in backend for the Akka gRPC client.
-
-Native HTTP/2 support in Akka gRPC reduces the number of upstream dependencies and enables more deeply integrated tooling for Akka gRPC in the future.
-
-For now, a connection-level and a "persistent connection" API is provided. The entry points are very similar to the existing flow-based HTTP/1 client APIs (responses are provided out-of-order, though, see the docs). The persistent connection API provides functionality similar to the `newHostConnectionPool` API.
-
-Higher-level APIs for HTTP/2 like the `superPool` or `singleRequest` APIs (or a potential automatic integration into the existing APIs) are still discussed.
-
-Please see the @ref[documentation](../client-side/http2.md) for more information and usage examples.
-
-Other notable changes:
-
-#### akka-http-core
-
-* Better support for filename in Content-Disposition [#3705](https://github.com/akka/akka-http/pull/3705)
-* Warn if trying to bind flow/source with HTTP2 (which is not supported) [#3678](https://github.com/akka/akka-http/pull/3678)
-
-#### akka-http-testkit
-
-* Fetch chunks in the testkit without waiting for the whole response to finish [#3724](https://github.com/akka/akka-http/pull/3724)
-
-#### docs
-
-* Show examples of using the Akka HTTP BOM (bill of materials) in dependency blocks
-
-## 10.2.2
-
-This release includes a number of improvements to the HTTP/2 server support,
-while we continue to prepare for providing HTTP/2 support at the client as
-well.
-
-As of this version, it is no longer strictly necessary to depend no a separate
-'akka-http2-support' artifact to get HTTP/2 support in Akka HTTP. We will
-continue to publish an empty artifact with that name to make it easy to
-upgrade, however.
-
-### Changes since 10.2.1
-
-#### akka-http-core
-
-* Allow illegal header keys to be ignored [#3133](https://github.com/akka/akka-http/pull/3133)
-* `HttpCookie.copy` was calling itself recursively [#3670](https://github.com/akka/akka-http/pull/3670)
-* Don't dispatch onResponseEntity... events for entities that don't have to be subscribed [#3574](https://github.com/akka/akka-http/pull/3574)
-* Add modeled 'TE' header [#3616](https://github.com/akka/akka-http/pull/3616), [#3618](https://github.com/akka/akka-http/pull/3618)
-* Add parens to deprecation messages for bind-methods [#3547](https://github.com/akka/akka-http/pull/3547)
-* Use official version of SocketUtil in tests [#3558](https://github.com/akka/akka-http/pull/3558)
-* Link to https rather than http [#3663](https://github.com/akka/akka-http/pull/3663)
-* Avoid `temporaryServerHostnameAndPort` [#3691](https://github.com/akka/akka-http/pull/3691)
-
-#### akka-http
-
-* Optimize header directives by avoiding `HttpHeader.unapply` [#3591](https://github.com/akka/akka-http/pull/3591)
-
-#### akka-http-marshallers
-
-* Update jackson-dataformat-xml from 2.10.5 to 2.10.5.1 [#3695](https://github.com/akka/akka-http/pull/3695)
-
-#### akka-http-testkit
-
-* Fall through on AssertionErrors in testkit [#3512](https://github.com/akka/akka-http/pull/3512)
-* Fail noisily if trying to use `~>` together with `transparent-head-requests` [#3569](https://github.com/akka/akka-http/pull/3569)
-
-#### docs
-
-* Add example for Get request with query parameters [#3624](https://github.com/akka/akka-http/pull/3624)
-* Add akka-actor-typed dependency to introduction.md [#3565](https://github.com/akka/akka-http/pull/3565)
-* Typo fix: "the onne" --> "the one" [#3521](https://github.com/akka/akka-http/pull/3521)
-* Some docs gardening [#3544](https://github.com/akka/akka-http/pull/3544)
-* Link project info to snapshots [#3681](https://github.com/akka/akka-http/pull/3681)
-* Release notes for 10.1.13 [#3635](https://github.com/akka/akka-http/pull/3635)
-* Add section about how to configure snapshots [#3642](https://github.com/akka/akka-http/pull/3642)
-* Add example for `Get` request with query parameters [#3624](https://github.com/akka/akka-http/pull/3624)
-* Update `formFields` example [#3650](https://github.com/akka/akka-http/pull/3650)
-* Verify signatures from the markdown actually exist [#3654](https://github.com/akka/akka-http/pull/3654)
-* Add link from `formFields` to `parameters` directive docs [#3655](https://github.com/akka/akka-http/pull/3655)
-* Use explicit paths to snippets [#3653](https://github.com/akka/akka-http/pull/3653)
-* Fix the `Bid` class. [#3661](https://github.com/akka/akka-http/pull/3661)
-
-#### akka-http2-support
-
-* Extract common rendering + add userAgent on requests [#3657](https://github.com/akka/akka-http/pull/3657)
-* Continue accepting window updates even when done sending [#3619](https://github.com/akka/akka-http/pull/3619)
-* Support custom HTTP methods for HTTP/2 [#3622](https://github.com/akka/akka-http/pull/3622)
-* More robust handling of IncomingStreamBuffer.onPull [#3621](https://github.com/akka/akka-http/pull/3621)
-* Simplify `Http2Substream` hierarchy trading a bit of type-safety for simplicity [#3605](https://github.com/akka/akka-http/pull/3605)
-* More useful event info for stream state changes [#3643](https://github.com/akka/akka-http/pull/3643)
-* Add some more basic HTTP/2 client tests [#3644](https://github.com/akka/akka-http/pull/3644)
-* Configurable ping support through demuxer [#3617](https://github.com/akka/akka-http/pull/3617)
-* Close the substreams earlier from the demuxer [#3647](https://github.com/akka/akka-http/pull/3647)
-* HTTP/2 client test coverage (and support for) TLS session info [#3668](https://github.com/akka/akka-http/pull/3668)
-* Handle RST while sending data + more tests [#3671](https://github.com/akka/akka-http/pull/3671)
-* Fix lost 'pull' when closing while waiting for window [#3672](https://github.com/akka/akka-http/pull/3672)
-* Send and enforce max concurrent streams setting [#3529](https://github.com/akka/akka-http/pull/3529)
-* Unify incoming and outgoing state machine [#3552](https://github.com/akka/akka-http/pull/3552)
-* Disable Push (send SETTING) [#3555](https://github.com/akka/akka-http/pull/3555)
-* Fix Scala 2.12 compilation error [#3582](https://github.com/akka/akka-http/pull/3582)
-* Remove explicit parallelism parameter in HTTP/2 [#3545](https://github.com/akka/akka-http/pull/3545)
-* Respect remote max concurrent streams (reprise) [#3581](https://github.com/akka/akka-http/pull/3581)
-* Also go through state machine for `resetStream` [#3584](https://github.com/akka/akka-http/pull/3584)
-* Fix leakage of incoming substreams in edge cases [#3233](https://github.com/akka/akka-http/pull/3233)
-* Run handler code in its own task on the server [#3593](https://github.com/akka/akka-http/pull/3593)
-* Check HTTP2 headers for correctness [#3603](https://github.com/akka/akka-http/pull/3603)
-* HTTP/2 connection level API [#3511](https://github.com/akka/akka-http/pull/3511)
-* Accepting trailing headers in the HTTP/2 client [#3602](https://github.com/akka/akka-http/pull/3602)
-* Protocol-level client specs [#3532](https://github.com/akka/akka-http/pull/3532)
-* Move some public API bits to its final places and mark them as `@ApiMayChange`[#3526](https://github.com/akka/akka-http/pull/3526)
-* Use LogHelper in demux classes [#3506](https://github.com/akka/akka-http/pull/3506)
-* Remove some minor repetition in HTTP/2 rendering [#3229](https://github.com/akka/akka-http/pull/3229)
-* Test server responses to invalid ping frames [#3523](https://github.com/akka/akka-http/pull/3523)
-* Use scheme portion of target URI in `:scheme` pseudo-header [#3535](https://github.com/akka/akka-http/pull/3535)
-* Add test for receiving `WINDOW_UPDATE` in `HalfClosedRemoteWaitingForOutgoingStream` state [#3554](https://github.com/akka/akka-http/pull/3554)
-* Make 'network' and 'user' sides more explicit [#3638](https://github.com/akka/akka-http/pull/3638)
-* `streamId` attribute is not needed / supported on client side [#3652](https://github.com/akka/akka-http/pull/3652)
-
-#### build
-
-* Akka HTTP BOM [#3665](https://github.com/akka/akka-http/pull/3665)
-* Add 10.2.1 to MiMa [#3499](https://github.com/akka/akka-http/pull/3499)
-* Increase paradox parsing timeout [#3508](https://github.com/akka/akka-http/pull/3508)
-* Also aggregate akka-http-bench-jmh, to fail if benchs fail to compile [#3561](https://github.com/akka/akka-http/pull/3561)
-* Exclude akka-http-bench-jmh from whitesource [#3562](https://github.com/akka/akka-http/pull/3562)
-* Disable whitesource for submodules which are not to be published [#3564](https://github.com/akka/akka-http/pull/3564)
-* Remove sbt-javaagent [#3598](https://github.com/akka/akka-http/pull/3598)
-* Include stack traces in scalatest failures [#3612](https://github.com/akka/akka-http/pull/3612)
-* Add 10.1.13 to mima [#3641](https://github.com/akka/akka-http/pull/3641)
-
-And various updates:
-
-* Update akka to 2.5.32 [#3558](https://github.com/akka/akka-http/pull/3558)
-* Update caffeine from 2.8.5 to 2.8.7 [#3515](https://github.com/akka/akka-http/pull/3515)
-* Update junit from 4.12 to 4.13.1 [#3517](https://github.com/akka/akka-http/pull/3517)
-* Update paradox-theme-akka, ... from 0.35 to 0.36[#3697](https://github.com/akka/akka-http/pull/3697)
-* Update sbt-bintray from 0.5.6 to 0.6.1 [#3572](https://github.com/akka/akka-http/pull/3572), [#3596](https://github.com/akka/akka-http/pull/3596)
-* Update sbt-mima-plugin from 0.8.0 to 0.8.1 [#3548](https://github.com/akka/akka-http/pull/3548)
-* Update sbt-scalafix, scalafix-core, ... from 0.9.21 to 0.9.23 [#3614](https://github.com/akka/akka-http/pull/3614)
-* Update specs2-core from 4.10.3 to 4.10.5 [#3518](https://github.com/akka/akka-http/pull/3518), [#3550](https://github.com/akka/akka-http/pull/3550)
-* Update spray-json from 1.3.5 to 1.3.6 [#3629](https://github.com/akka/akka-http/pull/3629)
-
-## 10.2.1
-
-This release includes:
-
-* Improved source-compatibility with Akka HTTP 10.1.x [#3489](https://github.com/akka/akka-http/pull/3489)
-* Re-introduction of the lingerTimeout option [#3456](https://github.com/akka/akka-http/pull/3456)
-
-### Changes since 10.2.0
-
-#### akka-http-core
-
-* Reenable lingerTimeout [#3456](https://github.com/akka/akka-http/pull/3456)
-* Make entities of HEAD requests discard [#3440](https://github.com/akka/akka-http/pull/3440)
-* Fix HTTPS proxy CONNECT request [#3434](https://github.com/akka/akka-http/pull/3434)
-* Expose the SslSession via an attribute [#3472](https://github.com/akka/akka-http/pull/3472)
-* Add debug logging when Websocket impl closes connections after timeout [#3431](https://github.com/akka/akka-http/pull/3431)
-* Spelling in reference.conf [#3425](https://github.com/akka/akka-http/pull/3425)
-* Remove unused import in Handshake class [#3464](https://github.com/akka/akka-http/pull/3464)
-* Tests: use copy of SocketUtil that does not use 127.x.y.255 addresses [#3460](https://github.com/akka/akka-http/pull/3460)
-
-#### akka-http
-
-* Provide implicit conversion from route and materializer to flow [#3489](https://github.com/akka/akka-http/pull/3489)
-* Fail storeUploadedFile(s) directive when IO operation fails [#3437](https://github.com/akka/akka-http/pull/3437)
-* Fix Route.handlerFlow deprecation message [#3465](https://github.com/akka/akka-http/pull/3465)
-* Fix a couple of warnings [#3482](https://github.com/akka/akka-http/pull/3482)
-* Clean up some imports [#3457](https://github.com/akka/akka-http/pull/3457)
-
-#### docs
-
-* Docs for getting data from a strict entity in a client [#3446](https://github.com/akka/akka-http/pull/3446)
-* Fix links to httpsServer / httpsClient [#3453](https://github.com/akka/akka-http/pull/3453)
-* Fix typo in deprecation message [#3424](https://github.com/akka/akka-http/pull/3424)
-* Update Scala style guide example to match the Java one (remove duplicated "customer" path) [#3448](https://github.com/akka/akka-http/pull/3448)
-* Document how to disable hostname verification without ssl-config [#3483](https://github.com/akka/akka-http/pull/3483)
-* Fix introduction markup [#3476](https://github.com/akka/akka-http/pull/3476)
-* Update head documentation about default behavior [#3480](https://github.com/akka/akka-http/pull/3480)
-* Document requiring client authentication [#3492](https://github.com/akka/akka-http/pull/3492)
-* Update websocket docs to describe attribute [#3488](https://github.com/akka/akka-http/pull/3488)
-
-#### akka-http2-support
-
-* Ignore unexpected DATA frames in state closed [#3462](https://github.com/akka/akka-http/pull/3462)
-* Improve HTTP2 debug logging [#3467](https://github.com/akka/akka-http/pull/3467)
-
-#### build
-
-* Set up mima for 10.2 [#3408](https://github.com/akka/akka-http/pull/3408)
-* Simplify http-core test against akka master scenario [#3402](https://github.com/akka/akka-http/pull/3402)
-* Increase paradox parsing timeout [#3430](https://github.com/akka/akka-http/pull/3430)
-* Update to Scala 2.12.12 [#3420](https://github.com/akka/akka-http/pull/3420)
-* Update github-api from 1.115 to 1.116 [#3443](https://github.com/akka/akka-http/pull/3443)
-* Update sbt-jmh from 0.3.7 to 0.4.0 [#3471](https://github.com/akka/akka-http/pull/3471)
-* Update sbt-mima-plugin from 0.7.0 to 0.8.0 [#3475](https://github.com/akka/akka-http/pull/3475)
-* Update sbt-scalafix, scalafix-core, ... from 0.9.20 to 0.9.21 [#3479](https://github.com/akka/akka-http/pull/3479)
-* Update scalatest from 3.1.3 to 3.1.4 [#3454](https://github.com/akka/akka-http/pull/3454)
-* Update silencer-lib, silencer-plugin from 1.7.0 to 1.7.1 [#3397](https://github.com/akka/akka-http/pull/3397)
-* Update specs2-core from 4.10.2 to 4.10.3 [#3445](https://github.com/akka/akka-http/pull/3445)
-
-## 10.2.0
-
-Akka Http 10.2 is a modernization release to improve the integration with the latest Akka versions, streamline APIs, and improve performance.
-
-Since the original release of 10.1, the Akka project has introduced a few important features:
-
- * Akka 2.6 offers typed actors and ActorSystems
- * Akka Stream APIs were improved to work without requiring a `Materializer` in most cases
- * Akka gRPC 1.0 has been released which is built on top of Akka HTTP
-
-Akka Http 10.2.0 supports these changes in the following ways:
-
- * Http APIs now work the same whether a classic or a typed ActorSystem is provided
- * A new concise API for binding servers has been introduced
- * A new set of directives @ref[handle](../routing-dsl/directives/route-directives/handle.md), and @ref[handleSync](../routing-dsl/directives/route-directives/handleSync.md)
- provide more options to seamlessly mix Akka gRPC generated service handlers with Akka Http routes. HTTP/2 support has been improved based on Akka gRPC usage.
- * Akka HTTP now supports Akka Coordinated Shutdown for server bindings.
-
-### Seamless integration with Akka 2.6 and new server API entrypoints
-
-Making changes to support Akka 2.6 better, we realized that the existing server API is sometimes awkward to use and to evolve. Therefore, we took the opportunity to come up
-with a new @ref[ServerBuilder API](../migration-guide/migration-guide-10.2.x.md#new-serverbuilder-api-to-create-server-bindings) that provides a way to bind servers more
-concisely, especially from Java.
-
-Code like:
-
-Scala
-: @@snip [AkkaHttp1020MigrationSpec.scala](/docs/src/test/scala/docs/http/scaladsl/server/AkkaHttp1020MigrationSpec.scala) { #old-binding }
-
-Java
-: @@snip [AkkaHttp1020MigrationExample.java](/docs/src/test/java/docs/http/javadsl/server/AkkaHttp1020MigrationExample.java) { #old-binding }
-
-can now be written as:
-
-Scala
-: @@snip [AkkaHttp1020MigrationSpec.scala](/docs/src/test/scala/docs/http/scaladsl/server/AkkaHttp1020MigrationSpec.scala) { #new-binding }
-
-Java
-: @@snip [AkkaHttp1020MigrationExample.java](/docs/src/test/java/docs/http/javadsl/server/AkkaHttp1020MigrationExample.java) { #new-binding }
-
-Notably, server written with the routing DSL will now be automatically converted to an asynchronous handler (using the new pendant of `bindAndHandleAsync`) instead of
-being provided as a Flow (using `bindAndHandle` before). This has the benefit that it fits the style of the routing DSL better which really represents an asynchronous handler
-function and, more importantly, will enable routes to work automatically with HTTP/2 (when enabled).
-
-The old APIs have been deprecated but will be kept for binary and source compatibility at least until 10.3 but maybe even longer (because they have been such a central part).
-
-We made an effort to keep supporting Akka 2.5.x (>= 2.5.31) for this release to ease the migration burden. It required backporting some features from Akka 2.6 so that
-seamless APIs would work the same with Akka 2.6 and Akka 2.5. The 10.2.x release line will be the last supporting Akka 2.5.
-
-To do the migration you can run the following task in sbt if you have scalafix enabled in your project:
-
-```
-scalafixAll dependency:MigrateToServerBuilder@com.typesafe.akka:akka-http-scalafix-rules:10.2.0
-```
-
-See the @ref[migration notes](../migration-guide/migration-guide-10.2.x.md#akka-http-10-1-x-10-2-0) for more information about how to setup and use scalafix to do the migration.
-
-### Routing DSL guidelines
-
-Akka HTTP's routing DSL comes with great power once you have mastered it. However, the flexibility it provides can be hard to tame for new users or when
-projects grow. We acknowledge these difficulties and want to conquer them with giving more guidelines to get started with building routes more
-easily. For that reason, we created two new documentation pages to give advice about how routes can be organized for scale:
-
- * The new @ref[styleguide](../routing-dsl/style-guide.md) gives general recommendations about how to structure route source code.
- * A @ref[comparison with Play routes](../routing-dsl/play-comparison.md) gives a side-by-side overview of how routing features of Play and Akka HTTP compare to
- each other.
-
-### Attributes for HttpRequest and HttpResponse
-
-In many cases metadata needs to be attached to an HTTP message. Previously, this was accomplished by introducing synthetic headers to add to requests and responses. However,
-this was more of a workaround that could lead to confusion about which headers should be rendered and where they originated. Akka Http 10.2 introduces attributes to HTTP messages.
-These allow attaching and querying typed metadata values to messages.
-
-See @ref[Attributes](../common/http-model.md#attributes) for more information.
-
-### Default configuration improvements
-
-Seldom used features have now been turned off by default:
-
- * Transparent HEAD support was disabled, see [#2088](https://github.com/akka/akka-http/issues/2088) and the @ref[migration notes](../migration-guide/migration-guide-10.2.x.md#transparent-head-requests-now-disabled-by-default) for information about the rationale.
- * Server-side HTTP pipelining was disabled by default. Common HTTP clients do not support it by default or have it disabled, so to reduce complexity in the common code paths
- the default `akka.http.server.pipelining-limit` was changed to `1`. See the @ref[migration notes](../migration-guide/migration-guide-10.2.x.md#server-side-http-pipelining-now-disabled-by-default) for more information.
-
-### Better support for upcoming Scala versions
-
-Scala 2.13 deprecated "adapted arguments" which were heavily used in the routing DSL with the magnet pattern. It allowed that a single method with a single argument could
-take any number of arguments in a typesafe fashion by relying on the Scala compiler to convert those arguments to a tuple of arguments. Since a while we generally try to reduce our usage
-of implicits and the magnet pattern to avoid complex compile error messages, long compile times, and complexity. With Akka Http 10.2 we made another effort to reduce our dependency on that
-language feature by providing a set of code-generated overloads for the methods in question to pave our way for upcoming Scala versions.
-
-See the @ref[migration guide](../migration-guide/migration-guide-10.2.x.md#parameters-formfields-scaladsl-) for more information.
-
-### Client: configurable setting overrides per target host
-
-It is now possible to set overrides for client settings per target host @ref[via configuration](../client-side/configuration.md#per-host-overrides). For example, if you use Akka HTTP client
-to access different services, it is now possible to tweak pool and connection parameters like the maximum number of concurrent connections (`max-connections`) on a per-target-host-basis.
-Thanks to [David Knapp / @Falmarri](https://github.com/Falmarri) for providing an initial implementation of that feature a long time ago.
-
-### Client: custom client DNS resolution transport
-
-By default, host name resolution is done in the IO layer when a connection attempt is made. In some cases, it can make sense to be able to customize the resolution, for example if
-there are multiple ip addresses returned for a DNS query, this could be used to implement custom DNS load balancing schemes. For that purpose, a new `ClientTransport.withCustomResolver` was
-introduced that allows providing custom resolution for each connection attempt.
-
-See the section about @ref[custom client DNS resolution schemes](../client-side/client-transport.md#custom-host-name-resolution-transport) for more information.
-
-### Performance improvements
-
- * Better performance for big client pools: Big client pools with more than 500 connections (`max-connections = 500` or more) suffered from a bad choice of datastructure with O(n²) access
- times, so bigger pools spent too much time just sifting through the internal data structures instead of doing useful work. This has been fixed and a nightly benchmark has been set
- up to track performance going forward.
- * Cheaper logging in client pools helps pools of all sizes by avoiding logging when DEBUG logging is disabled.
- * discardEntityBytes for strict entities is now a no-op while before streams were materialized.
-
-### Streamlined HTTPS configuration
-
-Akka HTTP no longer uses the HTTPS configuration configured with `ssl-config`
-by default. Instead, it will use the JRE defaults for client connections. For
-server connections you should create a @apidoc[HttpsConnectionContext] with
-the relevant configuration.
-
-See @ref[Configuring HTTPS connections](../migration-guide/migration-guide-10.2.x.md#configuring-https-connections) for more information.
-
-### Other changes
-
-* Various bug fixes, such as around [percent-encoding URI queries](https://github.com/akka/akka-http/pull/3003) and [parsing headers with unicode characters](https://github.com/akka/akka-http/issues/1484).
-* RouteTest can now run integration tests with `~!>` through full client/server infrastructure [#3014](https://github.com/akka/akka-http/pull/3014)
-* Various improvements to HTTP/2 support, driven by [Akka gRPC](https://doc.akka.io/docs/akka-grpc).
-* Remove legacy host connection pool including settings and tests [#3188](https://github.com/akka/akka-http/pull/3188)
-
-### Migration notes
-
-Support for Scala 2.11 has been dropped in this release. See the @ref[Migration guide](../migration-guide/migration-guide-10.2.x.md) for
-more information about other changes which might need migration.
-
-### Changes since 10.1.11
-
-#### akka-http-core
-
-* Fix cancellation race conditions on the client-side [#2965](https://github.com/akka/akka-http/pull/2965)
-* Silence outgoing request stream error [#2905](https://github.com/akka/akka-http/pull/2905)
-* Add SameSite attribute to Cookies [#2928](https://github.com/akka/akka-http/pull/2928)
-* Only catch NonFatal Exceptions [#2853](https://github.com/akka/akka-http/pull/2853)
-* Add coordinated shutdown support [#3142](https://github.com/akka/akka-http/pull/3142)
-* Percent-encode illegal chars when creating URI query [#3003](https://github.com/akka/akka-http/pull/3003)
-* Add the remote address in parse errors when possible [#2899](https://github.com/akka/akka-http/pull/2899)
-* Remove `UseHttp2` [#2896](https://github.com/akka/akka-http/pull/2896)
-* Hide body and headers by default in `HttpRequest#toString` and `HttpResponse#toString` [#2560](https://github.com/akka/akka-http/pull/2560)
-* Fix headers javadsl scaladoc [#2932](https://github.com/akka/akka-http/pull/2932)
-* Allow client setting overrides for target hosts in config [#2574](https://github.com/akka/akka-http/pull/2574)
-* Fix EOL detection for body part parsing [#2581](https://github.com/akka/akka-http/pull/2581)
-* Update javadsl bindAndHandle to take a Java function and System [#3223](https://github.com/akka/akka-http/pull/3223)
-* Identify Content-Type `charset` parameter even if not lower case [#2926](https://github.com/akka/akka-http/pull/2926)
-* Prevent initialization NPE which might fail all retries quickly [#2958](https://github.com/akka/akka-http/pull/2958)
-* Add exclusion for Extension issues when building against Akka 2.6 [#2945](https://github.com/akka/akka-http/pull/2945)
-* Nest correctly in NewHostConnectionPool [#2964](https://github.com/akka/akka-http/pull/2964)
-* Support for request/response message attributes [#2938](https://github.com/akka/akka-http/pull/2938)
-* Don't fail slot after previous connection failed in special condition [#3021](https://github.com/akka/akka-http/pull/3021)
-* Simplify route2HandlerFlow [#2893](https://github.com/akka/akka-http/pull/2893)
-* Better support for the new Actors API [#3036](https://github.com/akka/akka-http/pull/3036)
-* Parse empty query `?` to `Query.empty` [#3042](https://github.com/akka/akka-http/pull/3042)
-* Make sure to cancel response entity on failure [#3046](https://github.com/akka/akka-http/pull/3046)
-* Add `akka.http.server.remote-address-attribute` [#2924](https://github.com/akka/akka-http/pull/2924)
-* Make `transparent-head-requests` opt-in [#3063](https://github.com/akka/akka-http/pull/3063)
-* Continue more gracefully when encountering multiple Host headers in a response [#3158](https://github.com/akka/akka-http/pull/3158)
-* Allow customizing parsing errors [#3049](https://github.com/akka/akka-http/pull/3049)
-* Don't extend from Char => Boolean for CharPredicate [#3107](https://github.com/akka/akka-http/pull/3107)
-* Add server-side streamCancellationDelay to mitigate cancellation race conditions [#2116](https://github.com/akka/akka-http/pull/2116)
-* Improve error message about unconsumed entity [#3109](https://github.com/akka/akka-http/pull/3109)
-* Header rendering with less indirection [#3106](https://github.com/akka/akka-http/pull/3106)
-* Remove deprecated methods taking implicit materializers [#3119](https://github.com/akka/akka-http/pull/3119)
-* Simplify `superPool` and `clientFlow` [#3156](https://github.com/akka/akka-http/pull/3156)
-* Deprecate Remote-Address header [#3174](https://github.com/akka/akka-http/pull/3174)
-* Move `max-content-length` definition from top to server/client [#3098](https://github.com/akka/akka-http/pull/3098)
-* Add test for failure propagation into websocket flows [#3276](https://github.com/akka/akka-http/pull/3276)
-* Deprecate UpgradeToWebSocket [#3278](https://github.com/akka/akka-http/pull/3278), [#3296](https://github.com/akka/akka-http/pull/3296)
-* Disable server-side HTTP pipelining by default[#](https://github.com/akka/akka-http/pull/)
-* Make HttpEntity.Strict.discardBytes a no-op [#3329](https://github.com/akka/akka-http/pull/3329)
-* Make sure to reset all UriParser fields before reusing[#](https://github.com/akka/akka-http/pull/)
-* Track idle slots explicitly to avoid O(n^2) work for big pools[#](https://github.com/akka/akka-http/pull/)
-* Keep request/response copy method public [#3347](https://github.com/akka/akka-http/pull/3347)
-* Introduce javadsl discardEntityBytes that takes a ClassicActorSystemProvider[#](https://github.com/akka/akka-http/pull/)
-* Provide toStrict overloads with ClassicActorSystemProvider parameter[#](https://github.com/akka/akka-http/pull/)
-* Introduce custom hostname resolution client transport [#3202](https://github.com/akka/akka-http/pull/3202)
-* Avoid expensive logging in NewHostConnectionPool [#3356](https://github.com/akka/akka-http/pull/3356)
-* Introduce Http().newServerAt server builder API[#](https://github.com/akka/akka-http/pull/)
-* Make HttpRequest/HttpResponse.hashCode depend on attributes [#3351](https://github.com/akka/akka-http/pull/3351)
-* Allow customization of materializer with new ServerBuider API[#3414](https://github.com/akka/akka-http/pull/3414)
-
-
-#### akka-http
-
-* Names as alternative to symbolic directive combiners [#3085](https://github.com/akka/akka-http/pull/3085)
-* Names for symbolic enhancements [#3082](https://github.com/akka/akka-http/pull/3082)
-* Allow names to match paths [#3089](https://github.com/akka/akka-http/pull/3089)
-* Remove deprecated FormFieldDirectives methods [#3120](https://github.com/akka/akka-http/pull/3120)
-* Remove magnets usage from formField directives [#3289](https://github.com/akka/akka-http/pull/3289)
-* Provide Route.toFunction as alternative to Route.asyncHandler [#3115](https://github.com/akka/akka-http/pull/3115)
-* New `handle` directive to create Route from function [#3239](https://github.com/akka/akka-http/pull/3239)
-* Allow 'bindAndHandleAsync' to take a 'Route' [#3237](https://github.com/akka/akka-http/pull/3237)
-* Make X-Real-IP take precedence over Remote-Address [#3173](https://github.com/akka/akka-http/pull/3173)
-* Allow passing a companion object to headerValueByType [#3279](https://github.com/akka/akka-http/pull/3279)
-* Replace magnetic parameter overloads by boilerplate-generated overloads [#2971](https://github.com/akka/akka-http/pull/2971)
-* Deprecate directives taking `Symbol` as argument [#3291](https://github.com/akka/akka-http/pull/3291)
-* Remove uploadedFile (deprecated in 10.0.11) [#3118](https://github.com/akka/akka-http/pull/3118)
-* Deprecate internal parts of coding infrastructure [#3262](https://github.com/akka/akka-http/pull/3262)
-* Deprecate HttpApp [#3162](https://github.com/akka/akka-http/pull/3162)
-* Allow 'complete' directive with status without adapted arguments [#3307](https://github.com/akka/akka-http/pull/3307)
-* Fix remaining internal adapted arguments warnings [#3337](https://github.com/akka/akka-http/pull/3337)
-* Create Unmarshaller.unmarshal overloads taking in ClassActorSystemProvider[#](https://github.com/akka/akka-http/pull/)
-* Add directives for extracting attributes [#3355](https://github.com/akka/akka-http/pull/3355)
-* Document and dogfood using the attribute for websockets [#3358](https://github.com/akka/akka-http/pull/3358)
-* Add handlePF directive [#3367](https://github.com/akka/akka-http/pull/3367)
-
-
-#### akka-http-marshallers
-
-* Only show unmarshalling error details when 'verbose-error-messages' is on [#3265](https://github.com/akka/akka-http/pull/3265)
-* Jackson: Better JSON validation error when unmarshalling [#2901](https://github.com/akka/akka-http/pull/2901)
-
-#### akka-http-testkit
-
-* Allow `RouteTest` to run integration tests via `~!>` operator [#3014](https://github.com/akka/akka-http/pull/3014)
-* Update to Scalatest 3.1.0 [#2851](https://github.com/akka/akka-http/pull/2851)
-* Handle test exceptions separately from regular exceptions [#2949](https://github.com/akka/akka-http/pull/2949)
-* Simplify implicits for RouteTest [#3060](https://github.com/akka/akka-http/pull/3060)
-* Fix more Scala 2.13 warnings [#3130](https://github.com/akka/akka-http/pull/3130)
-
-#### docs
-
-* Use typed ActorSystem in examples [#3242](https://github.com/akka/akka-http/pull/3242)
-* Routing DSL style guide [#3099](https://github.com/akka/akka-http/pull/3099)
-* Routing DSL compared with Play routes [#3079](https://github.com/akka/akka-http/pull/3979)
-* Small typo in docs/src/main/paradox/common/marshalling.md [#2864](https://github.com/akka/akka-http/pull/2864)
-* Add warning on usage on extractClientIP [#2922](https://github.com/akka/akka-http/pull/2922)
-* Show `RequestBuilding` in client examples [#2968](https://github.com/akka/akka-http/pull/2968)
-* Don't claim that SNI is a security feature [#3257](https://github.com/akka/akka-http/pull/3257)
-* Update documentation and examples to Akka 2.6 [#2996](https://github.com/akka/akka-http/pull/2996)
-* Link to major/minor Akka docs [#3048](https://github.com/akka/akka-http/pull/3048)
-* Actor interop Java example [#3078](https://github.com/akka/akka-http/pull/3078)
-* Make Case class extraction example work with 2.13 [#3092](https://github.com/akka/akka-http/pull/3092)
-* Fix more Scala 2.13 warnings [#3130](https://github.com/akka/akka-http/pull/3130)
-* Update extractClientIP.md wrt `remote-address-attribute` [#3083](https://github.com/akka/akka-http/pull/3083)
-* Make `HttpServerWithActorsSample` more 2.6-style [#3077](https://github.com/akka/akka-http/pull/3077)
-* Show symbolic Akka version for dependencies [#3121](https://github.com/akka/akka-http/pull/3121)
-* Support native ALPN in JDK >=8u251 [#3117](https://github.com/akka/akka-http/pull/3117)
-* Use automatic root dir resolution for snip and signature [#3339](https://github.com/akka/akka-http/pull/3339)
-* Page about client-side configuration + per-host-overrides [#3338](https://github.com/akka/akka-http/pull/3338)
-* Document and dogfood using the attribute for websockets [#3358](https://github.com/akka/akka-http/pull/3358)
-* Add 'troubleshooting' page, populate with 'PRI' error message [#3384](https://github.com/akka/akka-http/pull/3384)
-
-#### akka-http2-support
-
-* Initial HTTP/2 client implementation bits [#3166](https://github.com/akka/akka-http/pull/3166)
-* Potential fix for idle timeouts in HTTP/2 [#2776](https://github.com/akka/akka-http/pull/2776)
-* Frame parsing: improve handling of unknown values [#3101](https://github.com/akka/akka-http/pull/3101)
-* Support native ALPN in JDK >=8u251 [#3117](https://github.com/akka/akka-http/pull/3117)
-* Fix HeaderCompression updating table size without giving notice to peer [#2891](https://github.com/akka/akka-http/pull/2891)
-* Reduce HTTP/2 buffer debug logging [#3025](https://github.com/akka/akka-http/pull/3025)
-* Accept RST on an already-half-closed HTTP/2 stream [#2976](https://github.com/akka/akka-http/pull/2976)
-* Gracefully discard unsupported h2 SETTINGS [#3053](https://github.com/akka/akka-http/pull/3053)
-* Make the HTTP/2 Stream ID an attribute [#3224](https://github.com/akka/akka-http/pull/3224)
-
-#### akka-http-caching
-
-* Harden ExpiringLfuCacheSpec [#2960](https://github.com/akka/akka-http/pull/2960)
-
-#### build
-
-* Fix project-info links to API docs [#2857](https://github.com/akka/akka-http/pull/2857)
-* Drop Scala 2.11 [#2589](https://github.com/akka/akka-http/pull/2589)
-* Build with Scala 2.13 by default [#3126](https://github.com/akka/akka-http/pull/3126)
-* Better diagnostics when validatePullRequest fails weirdly [#2904](https://github.com/akka/akka-http/pull/2904)
-* Test against published snapshots instead of source deps [#3055](https://github.com/akka/akka-http/pull/3055)
-* Enable some fatal warnings for docs [#3114](https://github.com/akka/akka-http/pull/3114)
-* Add sbt-reproducible-builds [#3165](https://github.com/akka/akka-http/pull/3165)
-* Publish docs from travis [#3328](https://github.com/akka/akka-http/pull/3328)
-* Scalafix rules to rewrite to new ServerBuilder API automatically [#3407](https://github.com/akka/akka-http/pull/3407)
diff --git a/docs/src/main/paradox/release-notes/index.md b/docs/src/main/paradox/release-notes/index.md
index ace5b6953..b9292fd49 100644
--- a/docs/src/main/paradox/release-notes/index.md
+++ b/docs/src/main/paradox/release-notes/index.md
@@ -2,10 +2,4 @@
@@toc { depth=2 }
-@@@ index
-
-* [10.2.x](10.2.x.md)
-* [10.1.x](10.1.x.md)
-* [10.0.x](10.0.x.md)
-
-@@@
+* [Akka HTTP releases](https://doc.akka.io/docs/akka-http/10.2/release-notes/index.html)
diff --git a/docs/src/main/paradox/routing-dsl/directives/basic-directives/extractMaterializer.md b/docs/src/main/paradox/routing-dsl/directives/basic-directives/extractMaterializer.md
index ed4ff4b38..2e49fd2ce 100644
--- a/docs/src/main/paradox/routing-dsl/directives/basic-directives/extractMaterializer.md
+++ b/docs/src/main/paradox/routing-dsl/directives/basic-directives/extractMaterializer.md
@@ -11,7 +11,7 @@
## Description
Extracts the @apidoc[Materializer] from the @apidoc[RequestContext], which can be useful when you want to run an
-Akka Stream directly in your route.
+Apache Pekko Stream directly in your route.
See also @ref[withMaterializer](withMaterializer.md) to see how to customise the used materializer for specific inner routes.
diff --git a/docs/src/main/paradox/routing-dsl/directives/caching-directives/index.md b/docs/src/main/paradox/routing-dsl/directives/caching-directives/index.md
index 837c1e99d..7fb4d7e64 100644
--- a/docs/src/main/paradox/routing-dsl/directives/caching-directives/index.md
+++ b/docs/src/main/paradox/routing-dsl/directives/caching-directives/index.md
@@ -11,12 +11,12 @@ caching support works.
To use Apache Pekko HTTP Caching, add the module to your project:
@@dependency[sbt,Gradle,Maven] {
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol="PekkoHttpVersion"
value="$project.version$"
group="org.apache.pekko"
artifact="pekko-http-caching_$scala.binary.version$"
- version="AkkaHttpVersion"
+ version="PekkoHttpVersion"
}
## Imports
diff --git a/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromBrowseableDirectory.md b/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromBrowseableDirectory.md
index 9bdfd5cdf..1c10247eb 100644
--- a/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromBrowseableDirectory.md
+++ b/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromBrowseableDirectory.md
@@ -41,5 +41,5 @@ and renders a listing which looks like this:
>
Example page rendered by the `defaultDirectoryRenderer`.
-It's possible to turn off rendering the footer stating which version of Akka HTTP is rendering this page by configuring
+It's possible to turn off rendering the footer stating which version of Apache Pekko HTTP is rendering this page by configuring
the `akka.http.routing.render-vanity-footer` configuration option to `off`.
\ No newline at end of file
diff --git a/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromDirectory.md b/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromDirectory.md
index 7fefb1ff1..bce66a6b6 100644
--- a/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromDirectory.md
+++ b/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromDirectory.md
@@ -22,10 +22,10 @@ To serve files from a classpath directory use @ref[getFromResourceDirectory](get
Note that it's not required to wrap this directive with `get` as this directive will only respond to `GET` requests.
@@@ note
-The file's contents will be read using an Akka Streams *`Source`* which *automatically uses
+The file's contents will be read using an Apache Pekko Streams *`Source`* which *automatically uses
a pre-configured dedicated blocking io dispatcher*, which separates the blocking file operations from the rest of the stream.
-Note also that thanks to using Akka Streams internally, the file will be served at the highest speed reachable by
+Note also that thanks to using Apache Pekko Streams internally, the file will be served at the highest speed reachable by
the client, and not faster – i.e. the file will *not* end up being loaded in full into memory before writing it to
the client.
@@@
diff --git a/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromFile.md b/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromFile.md
index 0a3e80d70..f6fab0a57 100644
--- a/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromFile.md
+++ b/docs/src/main/paradox/routing-dsl/directives/file-and-resource-directives/getFromFile.md
@@ -22,10 +22,10 @@ To serve files from a classpath directory use @ref[getFromResourceDirectory](get
Note that it's not required to wrap this directive with `get` as this directive will only respond to `GET` requests.
@@@ note
-The file's contents will be read using an Akka Streams *`Source`* which *automatically uses
+The file's contents will be read using an Apache Pekko Streams *`Source`* which *automatically uses
a pre-configured dedicated blocking io dispatcher*, which separates the blocking file operations from the rest of the stream.
-Note also that thanks to using Akka Streams internally, the file will be served at the highest speed reachable by
+Note also that thanks to using Apache Pekko Streams internally, the file will be served at the highest speed reachable by
the client, and not faster – i.e. the file will *not* end up being loaded in full into memory before writing it to
the client.
@@@
diff --git a/docs/src/main/paradox/routing-dsl/directives/future-directives/onCompleteWithBreaker.md b/docs/src/main/paradox/routing-dsl/directives/future-directives/onCompleteWithBreaker.md
index 0c87ad8fb..711c11cc3 100644
--- a/docs/src/main/paradox/routing-dsl/directives/future-directives/onCompleteWithBreaker.md
+++ b/docs/src/main/paradox/routing-dsl/directives/future-directives/onCompleteWithBreaker.md
@@ -11,7 +11,7 @@
## Description
Evaluates its parameter of type @scala[`Future[T]`]@java[`CompletionStage<T>`] protecting it with the specified @apidoc[CircuitBreaker].
-Refer to @extref[Circuit Breaker](akka-docs:common/circuitbreaker.html) for a detailed description of this pattern.
+Refer to @extref[Circuit Breaker](pekko-docs:common/circuitbreaker.html) for a detailed description of this pattern.
If the @apidoc[CircuitBreaker] is open, the request is rejected with a @apidoc[CircuitBreakerOpenRejection].
Note that in this case the request's entity databytes stream is cancelled, and the connection is closed
diff --git a/docs/src/main/paradox/routing-dsl/directives/method-directives/head.md b/docs/src/main/paradox/routing-dsl/directives/method-directives/head.md
index e9f936184..c8cd2722e 100644
--- a/docs/src/main/paradox/routing-dsl/directives/method-directives/head.md
+++ b/docs/src/main/paradox/routing-dsl/directives/method-directives/head.md
@@ -18,7 +18,7 @@ method `HEAD` are passed on to the inner route. All others are rejected with a
by the default @ref[RejectionHandler](../../rejections.md#the-rejectionhandler).
@@@ note
-Akka HTTP can handle HEAD requests transparently by dispatching a GET request to the handler and
+Apache Pekko HTTP can handle HEAD requests transparently by dispatching a GET request to the handler and
stripping off the result body. See the `akka.http.server.transparent-head-requests` setting for how to enable
this behavior.
@@@
diff --git a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasic.md b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasic.md
index 1728bc458..dd1585865 100644
--- a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasic.md
+++ b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasic.md
@@ -20,7 +20,7 @@ respectively applies the inner route or rejects the request with a @apidoc[Authe
which by default is mapped to an `401 Unauthorized` response.
Longer-running authentication tasks (like looking up credentials in a database) should use the @ref[authenticateBasicAsync](authenticateBasicAsync.md)
-variant of this directive which allows it to run without blocking routing layer of Akka HTTP, freeing it for other requests.
+variant of this directive which allows it to run without blocking routing layer of Apache Pekko HTTP, freeing it for other requests.
Standard HTTP-based authentication which uses the `WWW-Authenticate` header containing challenge data and
@apidoc[Authorization] header for receiving credentials is implemented in `authenticateOrRejectWithChallenge`.
diff --git a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasicAsync.md b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasicAsync.md
index 133c6df6b..ba37128c1 100644
--- a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasicAsync.md
+++ b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateBasicAsync.md
@@ -14,7 +14,7 @@
Wraps the inner route with Http Basic authentication support using a given @scala[@scaladoc[AsyncAuthenticator[T]](akka.http.scaladsl.server.Directives#AsyncAuthenticator[T]=akka.http.scaladsl.server.directives.Credentials=%3Escala.concurrent.Future[Option[T]])]@java[ `AsyncAuthenticator<T>` - function from `Optional<ProvidedCredentials>` to `CompletionStage<Optional<T>>`].
This variant of the @ref[authenticateBasic](authenticateBasic.md) directive returns a @scala[`Future[Option[T]]`]@java[`CompletionStage<Optional<T>>`] which allows freeing up the routing
-layer of Akka HTTP, freeing it for other requests. It should be used whenever an authentication is expected to take
+layer of Apache Pekko HTTP, freeing it for other requests. It should be used whenever an authentication is expected to take
a longer amount of time (e.g. looking up the user in a database).
In case the returned option is @scala[`None`]@java[an empty `Optional`] the request is rejected with a @apidoc[AuthenticationFailedRejection],
diff --git a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2.md b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2.md
index c35dcf37d..0d1e3a65d 100644
--- a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2.md
+++ b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2.md
@@ -26,7 +26,7 @@ respectively applies the inner route or rejects the request with a @apidoc[Authe
which by default is mapped to an `401 Unauthorized` response.
Longer-running authentication tasks (like looking up credentials in a database) should use the @ref[authenticateOAuth2Async](authenticateOAuth2Async.md)
-variant of this directive which allows it to run without blocking routing layer of Akka HTTP, freeing it for other requests.
+variant of this directive which allows it to run without blocking routing layer of Apache Pekko HTTP, freeing it for other requests.
See @ref[Credentials and password timing attacks](index.md#credentials-and-timing-attacks) for details about verifying the secret.
@@ -35,4 +35,4 @@ For more information on how OAuth2 works see [RFC 6750](https://tools.ietf.org/h
## Example
Usage in code is exactly the same as @ref[authenticateBasic](authenticateBasic.md),
-with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Akka HTTP itself).
+with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Apache Pekko HTTP itself).
diff --git a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2Async.md b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2Async.md
index c96de982b..c796d9e6a 100644
--- a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2Async.md
+++ b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2Async.md
@@ -34,4 +34,4 @@ For more information on how OAuth2 works see [RFC 6750](https://tools.ietf.org/h
## Example
Usage in code is exactly the same as @ref[authenticateBasicAsync](authenticateBasicAsync.md),
-with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Akka HTTP itself).
+with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Apache Pekko HTTP itself).
diff --git a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PF.md b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PF.md
index 293eae39d..81d1f8a7f 100644
--- a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PF.md
+++ b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PF.md
@@ -27,7 +27,7 @@ Its semantics are equivalent to `authenticateOAuth2PF` 's, where not handling a
leaves the request to be rejected with a @apidoc[AuthenticationFailedRejection] rejection.
Longer-running authentication tasks (like looking up credentials in a database) should use the @ref[authenticateOAuth2Async](authenticateOAuth2Async.md)
-variant of this directive which allows it to run without blocking routing layer of Akka HTTP, freeing it for other requests.
+variant of this directive which allows it to run without blocking routing layer of Apache Pekko HTTP, freeing it for other requests.
See @ref[Credentials and password timing attacks](index.md#credentials-and-timing-attacks) for details about verifying the secret.
@@ -36,4 +36,4 @@ For more information on how OAuth2 works see [RFC 6750](https://tools.ietf.org/h
## Example
Usage in code is exactly the same as @ref[authenticateBasicPF](authenticateBasicPF.md),
-with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Akka HTTP itself).
+with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Apache Pekko HTTP itself).
diff --git a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PFAsync.md b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PFAsync.md
index 92f8a6ac2..61982a40f 100644
--- a/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PFAsync.md
+++ b/docs/src/main/paradox/routing-dsl/directives/security-directives/authenticateOAuth2PFAsync.md
@@ -35,4 +35,4 @@ For more information on how OAuth2 works see [RFC 6750](https://tools.ietf.org/h
## Example
Usage in code is exactly the same as @ref[authenticateBasicPFAsync](authenticateBasicPFAsync.md),
-with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Akka HTTP itself).
+with the difference that one must validate the token as OAuth2 dictates (which is currently not part of Apache Pekko HTTP itself).
diff --git a/docs/src/main/paradox/routing-dsl/directives/security-directives/index.md b/docs/src/main/paradox/routing-dsl/directives/security-directives/index.md
index ae5fbfc46..401f600f7 100644
--- a/docs/src/main/paradox/routing-dsl/directives/security-directives/index.md
+++ b/docs/src/main/paradox/routing-dsl/directives/security-directives/index.md
@@ -48,12 +48,12 @@ authentication information. The general mechanism is defined in [RFC 7235](https
The "HTTP Authentication Scheme Registry" defines the namespace for the authentication schemes in challenges and
credentials. You can see the currently registered schemes at [IANA HTTP Authentication Scheme Registry](https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml).
-At this point Akka HTTP only implements the "'Basic' HTTP Authentication Scheme" whose most current specification can be
+At this point, Apache Pekko HTTP only implements the "'Basic' HTTP Authentication Scheme" whose most current specification can be
found here: <https://datatracker.ietf.org/doc/rfc7617/>.
## Low-level OAuth2 "Bearer Token" directives
-The OAuth2 directives currently provided in Akka HTTP are not a full OAuth2 protocol implementation,
+The OAuth2 directives currently provided in Apache Pekko HTTP are not a full OAuth2 protocol implementation,
they are only a means of extracting the so called `Bearer Token` from the @apidoc[Authorization] HTTP Header,
as defined in [RFC 6750](https://tools.ietf.org/html/rfc6750), and allow users to validate and complete the protocol.
diff --git a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/extractRequestTimeout.md b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/extractRequestTimeout.md
index 331076a74..49d9b3c47 100644
--- a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/extractRequestTimeout.md
+++ b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/extractRequestTimeout.md
@@ -17,7 +17,7 @@ Please note that this extracts the request timeout at the current moment, but th
See other timeout directives about raciness inherent to timeout directives.
@@@
-For more information about various timeouts in Akka HTTP see @ref[Akka HTTP Timeouts](../../../common/timeouts.md).
+For more information about various timeouts in Apache Pekko HTTP see @ref[Pekko HTTP Timeouts](../../../common/timeouts.md).
## Example
diff --git a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeout.md b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeout.md
index c7601db8a..103ed40ea 100644
--- a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeout.md
+++ b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeout.md
@@ -10,7 +10,7 @@
## Description
-This directive enables "late" (during request processing) control over the @ref[Request timeout](../../../common/timeouts.md#request-timeout) feature in Akka HTTP.
+This directive enables "late" (during request processing) control over the @ref[Request timeout](../../../common/timeouts.md#request-timeout) feature in Apache Pekko HTTP.
The timeout can be either loosened or made more tight using this directive, however one should be aware that it is
inherently racy (which may especially show with very tight timeouts) since a timeout may already have been triggered
@@ -36,7 +36,7 @@ or malicious attackers) and if needed tighten it using the directives – not th
@@@
-For more information about various timeouts in Akka HTTP see @ref[Akka HTTP Timeouts](../../../common/timeouts.md).
+For more information about various timeouts in Apache Pekko HTTP see @ref[Pekko HTTP Timeouts](../../../common/timeouts.md).
## Example
diff --git a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeoutResponse.md b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeoutResponse.md
index d6250c951..986eb1d0c 100644
--- a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeoutResponse.md
+++ b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withRequestTimeoutResponse.md
@@ -26,7 +26,7 @@ of request timeouts being measured in seconds it shouldn't be a problem in reali
@@@
-To learn more about various timeouts in Akka HTTP and how to configure them see @ref[Akka HTTP Timeouts](../../../common/timeouts.md).
+To learn more about various timeouts in Apache Pekko HTTP and how to configure them see @ref[Pekko HTTP Timeouts](../../../common/timeouts.md).
## Example
diff --git a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withoutRequestTimeout.md b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withoutRequestTimeout.md
index 12ae306cf..1baa31eb4 100644
--- a/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withoutRequestTimeout.md
+++ b/docs/src/main/paradox/routing-dsl/directives/timeout-directives/withoutRequestTimeout.md
@@ -10,7 +10,7 @@
## Description
-This directive enables "late" (during request processing) control over the @ref[Request timeout](../../../common/timeouts.md#request-timeout) feature in Akka HTTP.
+This directive enables "late" (during request processing) control over the @ref[Request timeout](../../../common/timeouts.md#request-timeout) feature in Apache Pekko HTTP.
It is not recommended to turn off request timeouts using this method as it is inherently racy and disabling request timeouts
basically turns off the safety net against programming mistakes that it provides.
@@ -21,7 +21,7 @@ we're measuring the timeout" is already in the past (the moment we started handl
timeout already was triggered before your directive had the chance to change it, an timeout may still be logged.
@@@
-For more information about various timeouts in Akka HTTP see @ref[Akka HTTP Timeouts](../../../common/timeouts.md).
+For more information about various timeouts in Apache Pekko HTTP see @ref[Pekko HTTP Timeouts](../../../common/timeouts.md).
## Example
diff --git a/docs/src/main/paradox/routing-dsl/exception-handling.md b/docs/src/main/paradox/routing-dsl/exception-handling.md
index 97cb5eb87..c1fa225ac 100644
--- a/docs/src/main/paradox/routing-dsl/exception-handling.md
+++ b/docs/src/main/paradox/routing-dsl/exception-handling.md
@@ -79,7 +79,7 @@ This is because exceptions are known to have a negative performance impact for c
when the depth of the call stack is significant (stack trace construction cost)
and when the handler is located far from the place of the throwable instantiation (stack unwinding costs).
-In a typical Akka application both these conditions are frequently true,
+In a typical Apache Pekko application both these conditions are frequently true,
so as a rule of thumb, you should try to minimize the number of `Throwable` instances
reaching the exception handler.
diff --git a/docs/src/main/paradox/routing-dsl/index.md b/docs/src/main/paradox/routing-dsl/index.md
index 736c59dd0..12f2d02d2 100644
--- a/docs/src/main/paradox/routing-dsl/index.md
+++ b/docs/src/main/paradox/routing-dsl/index.md
@@ -64,7 +64,7 @@ If you have been using Play framework's routes file notation before this @ref[Pl
<a name="interaction-with-akka-typed">
## Interaction with Actors
-The following example shows how to use Apache Pekko HTTP with Akka Actors.
+The following example shows how to use Apache Pekko HTTP with Apache Pekko Actors.
We will create a small web server responsible to record build jobs with its state and duration, query jobs by
id and status, and clear the job history.
@@ -142,7 +142,7 @@ Subsequent POST request to `/test` with body `{"id": 1}` will be responded with
## Handling HTTP Server failures in the High-Level API
There are various situations when failure may occur while initialising or running an Apache Pekko HTTP server.
-Akka by default will log all these failures, however sometimes one may want to react to failures in addition
+Apache Pekko by default will log all these failures, however sometimes one may want to react to failures in addition
to them just being logged, for example by shutting down the actor system, or notifying some external monitoring
end-point explicitly.
diff --git a/docs/src/main/paradox/routing-dsl/routes.md b/docs/src/main/paradox/routing-dsl/routes.md
index 7273ab51b..0741638f9 100644
--- a/docs/src/main/paradox/routing-dsl/routes.md
+++ b/docs/src/main/paradox/routing-dsl/routes.md
@@ -88,7 +88,7 @@ of either the incoming request, the outgoing response or both
* Route filtering, which only lets requests satisfying a given filter condition pass and rejects all others
* Route chaining, which tries a second route if a given first one was rejected
-The first two points are provided by so-called @ref[Directives](directives/index.md#directives) of which a large number is already predefined by Akka
+The first two points are provided by so-called @ref[Directives](directives/index.md#directives) of which a large number is already predefined by Apache Pekko
HTTP and is extensible with user code.
The last point is achieved with the `concat` method.
diff --git a/docs/src/main/paradox/routing-dsl/source-streaming-support.md b/docs/src/main/paradox/routing-dsl/source-streaming-support.md
index 4ec0dc320..9ff29f4ef 100644
--- a/docs/src/main/paradox/routing-dsl/source-streaming-support.md
+++ b/docs/src/main/paradox/routing-dsl/source-streaming-support.md
@@ -1,6 +1,6 @@
# Source Streaming
-Apache Pekko HTTP supports completing a request with an Akka @apidoc[Source[T, \_]], which makes it possible to easily build
+Apache Pekko HTTP supports completing a request with an Apache Pekko @apidoc[Source[T, \_]], which makes it possible to easily build
and consume streaming end-to-end APIs which apply back pressure throughout the entire stack.
It is possible to complete requests with raw @apidoc[Source[ByteString, \_]], however often it is more convenient to
@@ -42,7 +42,7 @@ In this example we implement an API representing an infinite stream of tweets, v
@@@ div { .group-scala }
Firstly, we'll need to get some additional marshalling infrastructure set up, that is able to marshal to and from an
-Akka Streams @apidoc[Source[T, \_]]. One such trait, containing the needed marshallers is `SprayJsonSupport`, which uses
+Apache Pekko Streams @apidoc[Source[T, \_]]. One such trait, containing the needed marshallers is `SprayJsonSupport`, which uses
`spray-json` (a high performance JSON parser library), and is shipped as part of Apache Pekko HTTP in the
`pekko-http-spray-json` module.
@@ -56,7 +56,7 @@ like to stream a different content type (for example plists or protobuf).
@@@ div { .group-java }
Firstly, we'll need to get some additional marshalling infrastructure set up, that is able to marshal to and from an
-Akka Streams @apidoc[Source[T, ?]]. Here we'll use the `Jackson` helper class from `pekko-http-jackson` (a separate library
+Apache Pekko Streams @apidoc[Source[T, ?]]. Here we'll use the `Jackson` helper class from `pekko-http-jackson` (a separate library
that you should add as a dependency if you want to use Jackson with Apache Pekko HTTP).
First we enable JSON Streaming by making an implicit @apidoc[EntityStreamingSupport] instance available (Step 1).
@@ -94,7 +94,7 @@ For example, in case of JSON Streaming, there isn't really one standard about re
to render multiple JSON objects in a line-by-line fashion (Twitter's streaming APIs for example), while others simply return
very large arrays, which could be streamed as well.
-Akka defaults to the second one (streaming a JSON Array), as it is correct JSON and clients not expecting
+Apache Pekko defaults to the second one (streaming a JSON Array), as it is correct JSON and clients not expecting
a streaming API would still be able to consume it in a naive way if they'd want to.
The line-by-line approach however is also pretty popular even though it is not valid JSON. Its simplicity for
@@ -132,7 +132,7 @@ the server and is feeding it with one line of measurement data.
In this example, we want to consume this data in a streaming fashion from the request entity and also apply
back pressure to the underlying TCP connection should the server be unable to cope with the rate of incoming data. Back pressure
-is automatically applied thanks to @extref[Akka Streams](akka-docs:stream/index.html).
+is automatically applied thanks to @extref[Apache Pekko Streams](pekko-docs:stream/index.html).
Scala
: @@snip [JsonStreamingExamplesSpec.scala](/docs/src/test/scala/docs/http/scaladsl/server/directives/JsonStreamingExamplesSpec.scala) { #measurement-model #measurement-format }
diff --git a/docs/src/main/paradox/routing-dsl/testkit.md b/docs/src/main/paradox/routing-dsl/testkit.md
index ca0f7e704..d11215f92 100644
--- a/docs/src/main/paradox/routing-dsl/testkit.md
+++ b/docs/src/main/paradox/routing-dsl/testkit.md
@@ -9,13 +9,13 @@ route logic easy and convenient. This "route test DSL" is made available with th
To use Apache Pekko HTTP TestKit, add the module to your project:
@@dependency [sbt,Gradle,Maven] {
- symbol1=AkkaVersion
+ symbol1=PekkoVersion
value1=$akka.version$
- bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="AkkaHttpVersion"
- symbol2="AkkaHttpVersion"
+ bomGroup2="org.apache.pekko" bomArtifact2="pekko-http-bom_$scala.binary.version$" bomVersionSymbols2="PekkoHttpVersion"
+ symbol2="PekkoHttpVersion"
value2="$project.version$"
- group1="org.apache.pekko" artifact1="pekko-stream-testkit_$scala.binary.version$" version1=AkkaVersion
- group2="org.apache.pekko" artifact2="pekko-http-testkit_$scala.binary.version$" version2="AkkaHttpVersion"
+ group1="org.apache.pekko" artifact1="pekko-stream-testkit_$scala.binary.version$" version1=PekkoVersion
+ group2="org.apache.pekko" artifact2="pekko-http-testkit_$scala.binary.version$" version2="PekkoHttpVersion"
}
## Usage
@@ -206,7 +206,7 @@ Java
The timeouts you consciously defined on your lightning fast development environment might be too tight for your, most
probably, high-loaded Continuous Integration server, invariably causing spurious failures. To account for such
situations, timeout durations can be scaled by a given factor on such environments. Check the
-@extref[Akka Docs](akka-docs:testing.html#accounting-for-slow-test-systems)
+@extref[Apache Pekko Docs](pekko-docs:testing.html#accounting-for-slow-test-systems)
for further information.
diff --git a/docs/src/main/paradox/security.md b/docs/src/main/paradox/security.md
index 2bc37d793..5438e5f29 100644
--- a/docs/src/main/paradox/security.md
+++ b/docs/src/main/paradox/security.md
@@ -1,52 +1,21 @@
# ! Security Announcements !
## Receiving Security Advisories
-The best way to receive any and all security announcements is to subscribe to the [Akka security list](https://groups.google.com/forum/#!forum/akka-security).
+The best way to receive any and all security announcements is to subscribe to the [Apache Announce Mailing List](https://lists.apache.org/list.html?announce@apache.org).
-The mailing list is very low traffic, and receives notifications only after security reports have been managed by the core team and fixes are publicly available.
+This mailing list has a reasonable level of traffic, and receives notifications only after security reports have been managed by the core Apache teams and fixes are publicly available.
+
+This mailing list also has announcements of releases for Apache projects.
## Reporting Vulnerabilities
We strongly encourage people to report such problems to our private security mailing list first, before disclosing them in a public forum.
-Following best-practice, we strongly encourage anyone to report potential security
-vulnerabilities to security@akka.io before disclosing them in a public forum like the mailing list or as a Github issue.
-
-Reports to this email address will be handled by our security team, who will work together with you
-to ensure that a fix can be provided without delay.
-
-## Fixed Security Vulnerabilities
-
-### Fixed in Akka HTTP 10.2.7
-
-* @ref:[CVE-2021-42697: Stack overflow while parsing User-Agent header with deeply nested comments](security/2021-CVE-2021-42697-stack-overflow-parsing-user-agent.md)
-
-### Fixed in Akka HTTP 10.2.4 & 10.1.14
-
-* @ref:[Incorrect handling of Transfer-Encoding header](security/2021-02-24-incorrect-handling-of-Transfer-Encoding-header.md)
-
-### Fixed in Akka HTTP 10.1.5 & 10.0.14
-
-* @ref:[Denial of Service via unlimited decoding with decodeRequest directive ("zip bomb")](security/2018-09-05-denial-of-service-via-decodeRequest.md)
-
-### Fixed in Akka HTTP 10.0.6 & 2.4.11.2
-
-* @ref:[Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service](security/2017-05-03-illegal-media-range-in-accept-header-causes-stackoverflowerror.md)
-
-### Fixed in Akka HTTP 10.0.2 & 2.4.11.1
-
-* @ref:[Denial-of-Service by stream leak on unconsumed closed connections](security/2017-01-23-denial-of-service-via-leak-on-unconsumed-closed-connections.md)
-
-### Fixed in Akka HTTP 2.4.11
-
-* @ref:[Directory Traversal Vulnerability Announcement](security/2016-09-30-windows-directory-traversal.md)
-
+Please follow the [guidelines](https://www.apache.org/security/) laid down by the Apache Security team.
-@@@ index
+Ideally, any issues affecting Apache Pekko and Pekko should be reported to Apache team first. We will share the
+report with the Lightbend Akka team.
- * [2020](security/2021.md)
- * [2018](security/2018.md)
- * [2017](security/2017.md)
- * [2016](security/2016.md)
+## References
-@@@
\ No newline at end of file
+ * [Akka HTTP security fixes](https://doc.akka.io/docs/akka-http/10.2/security.html)
diff --git a/docs/src/main/paradox/security/2016-09-30-windows-directory-traversal.md b/docs/src/main/paradox/security/2016-09-30-windows-directory-traversal.md
deleted file mode 100644
index f6b345bde..000000000
--- a/docs/src/main/paradox/security/2016-09-30-windows-directory-traversal.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Directory Traversal in FileDirectives
-
-## Date
-
-30 September 2016
-
-## Description
-
-On Windows akka-http’s `getFromDirectory`, `getFromBrowseableDirectory`, `getFromBrowseableDirectories`,
-and `listDirectoryContents` directives unintentionally allow access to directories and files outside of
-the specified directory.
-
-All directories and files on the same drive as the specified directory for which the server process has
-sufficient permissions may be downloaded or browsed. This can be easily exploited by using a specially
-crafted URI.
-
-For example, a specially crafted request `http://localhost:8080/%5c..%5c..%5c..%5c..%5c..%5c..%5c..%5c..%5c..%5cwindows/win.ini`
-when handled by one of the affected directives, could expose your win.ini (and potentially any other file) to the attacker.
-
-## Impact
-
-[Directory traversal attack](https://en.wikipedia.org/wiki/Directory_traversal_attack) in case the above vulnerable directives are used.
-
-## Affected Versions
-
-OS:
-
-- **Only Windows** operating systems are affected by this vulnerability.
-
-Versions:
-
-- akka-http-experimental **prior to** `2.4.11`
-- spray-routing and spray-routing-shapeless2 **prior to** `1.3.4`
-
-Affected directives:
-
-- `getFromDirectory`
-- `getFromBrowseableDirectory`
-- `getFromBrowseableDirectories`
-- `listDirectoryContents`
-
-## Fixed versions
-
-- akka-http-experimental `2.4.11`
-- akka-http-experimental `2.0.5` (legacy)
-- spray `1.3.4`
-
-The fixed versions are **binary-compatible** with each of the affected versions, please upgrade as soon as you can.
-
-## Recommendations
-
-Following best security practices it is furthermore recommended to run the web server
-process with user credentials with as few permissions as possible to prevent unintended file access.
-
-Furthermore, we suggest using Linux servers and/or containers for hosting Apache Pekko HTTP applications,
-as these OSes receive more scrutiny than any other OS just because of the overwhelming number of
-installations running on Linux.
-
-## Acknowledgements
-
-Many thanks go to @roikonen for reporting the problem, @2beaucoup for providing a fix and @rbudzko
-and @jypma for providing advice for fixing the problem.
diff --git a/docs/src/main/paradox/security/2016.md b/docs/src/main/paradox/security/2016.md
deleted file mode 100644
index aa59903a2..000000000
--- a/docs/src/main/paradox/security/2016.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# 2016
-
-@@ toc
-
-@@@ index
-
- * [Directory Traversal Vulnerability Announcement](2016-09-30-windows-directory-traversal.md)
-
-@@@
\ No newline at end of file
diff --git a/docs/src/main/paradox/security/2017-01-23-denial-of-service-via-leak-on-unconsumed-closed-connections.md b/docs/src/main/paradox/security/2017-01-23-denial-of-service-via-leak-on-unconsumed-closed-connections.md
deleted file mode 100644
index fd8d77427..000000000
--- a/docs/src/main/paradox/security/2017-01-23-denial-of-service-via-leak-on-unconsumed-closed-connections.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Denial-of-Service by stream leak on unconsumed closed connections
-
-## Date
-
-23 January 2017
-
-## Description of Vulnerability
-
-For requests containing request bodies (including request methods which would normally include entities like GET requests),
-a mistake in completion handling of a connection could lead to memory leaking after the connection had been closed before the
-entity was consumed. This may eventually lead to a failure of the system due to being out of memory.
-
-Please subscribe to the [akka-security](https://groups.google.com/forum/#!forum/akka-security) mailing list to be notified promptly about future security issues.
-
-## Severity
-
-The [CVSS](https://en.wikipedia.org/wiki/CVSS) score of this vulnerability is 6.4 (Medium), based on vector [AV:N/AC:L/Au:N/C:N/I:N/A:C/E:F/RL:OF/RC:C](https://nvd.nist.gov/vuln-metrics/cvss/v2-calculator?calculator&version=2&vector=%28AV:N/AC:L/Au:N/C:N/I:N/A:C/E:F/RL:OF/RC:C%29).
-
-## Affected Versions
-
-- (experimental) Akka HTTP `2.4.11` and prior,
-- (stable) Akka HTTP `10.0.1` and prior.
-
-## Fixed Versions
-
-We have prepared patches for the affected versions, and have released the following versions which resolve the issue:
-
-- Akka HTTP `2.4.11.1` (Scala 2.11)
-- Akka HTTP `10.0.2` (Scala 2.11, 2.12)
-
-The patched releases contain no other changes except the single patch that addresses the memory leak vulnerability.
-*Binary and source compatibility has been maintained so the upgrade procedure is as simple as changing the library dependency.*
-
-## Additional Important Information
-
-Note that Play and Lagom applications are not impacted by this vulnerability, regardless of whether they are using the Akka HTTP backend or the Netty backend.
-
-If you have any questions or need any help, please contact [support@lightbend.com](mailto:support@lightbend.com).
-
-## Acknowledgements
-
-We would like to thank Dmitry Kolesnikov & Lari Hotari for their thorough investigation and bringing this issue to our attention.
diff --git a/docs/src/main/paradox/security/2017-05-03-illegal-media-range-in-accept-header-causes-stackoverflowerror.md b/docs/src/main/paradox/security/2017-05-03-illegal-media-range-in-accept-header-causes-stackoverflowerror.md
deleted file mode 100644
index 09bc77ea0..000000000
--- a/docs/src/main/paradox/security/2017-05-03-illegal-media-range-in-accept-header-causes-stackoverflowerror.md
+++ /dev/null
@@ -1,50 +0,0 @@
-# Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service
-
-## Date
-
-3 May 2017
-
-## Description of Vulnerability
-
-Handling a request that carries an Accept header with an unsupported media range starting with a wildcard but having a specific subtype (e.g. `*/boom`) leads to a stack overflow during negotiation of the content type. Per default, stack overflows are treated as fatal errors, so that the JVM process will shut itself down immediately.
-
-Please subscribe to the [akka-security](https://groups.google.com/forum/#!forum/akka-security) mailing list to be notified promptly about future security issues.
-
-
-## Severity
-
-The CVSS score of this vulnerability is 7.8 (High), based on vector [(AV:N/AC:L/Au:N/C:N/I:N/A:C)](https://nvd.nist.gov/vuln-metrics/cvss/v2-calculator?vector=%28AV:N/AC:L/Au:N/C:N/I:N/A:C%29).
-
-## Impact
-
-All Akka HTTP servers using the high-level routing DSL are affected. The infinite recursion happens inside the `complete` directive which is used in every Akka HTTP application using the high-level DSL.
-
-A remote attacker that is able to send an HTTP request with such a malformed Accept header to an Akka HTTP application is able to cause a StackOverflowException and if the exception remains unhandled effectively shut down the server.
-
-Applications written using only the low-level API from akka-http-core but not the routing DSL are not affected.
-
-## Affected versions
-
-- akka-http prior to `10.0.6` and `2.4.11.2`
-
-Notably **not affected**:
-
-- Play Framework (regardless of used server backend)
-- Lagom Framework
-- Low-level akka-http-core APIs
-- Spray
-
-## Fixed versions
-
-- akka-http `10.0.6` (stable)
-- akka-http `2.4.11.2` (experimental) (please upgrade to the actively maintained `10.0.x` series though)
-
-Please note that the `2.4.11.2` release contains no other changes except the single patch that addresses the vulnerability. *Binary and source compatibility has been maintained so the upgrade procedure is as simple as changing the library dependency.*
-
-If you have any questions or need any help, please contact [support@lightbend.com](mailto:support@lightbend.com).
-
-## Acknowledgements
-
-We would like to thank Martins Rumkovskis for finding and reporting this vulnerability.
-
-At the same time we would like to remind our users that security related issues should be reported using our [security@akka.io](mailto:security@akka.io) alias, such that we can prevent a vulnerability from being exploited while we work on a workaround or fix.
diff --git a/docs/src/main/paradox/security/2017.md b/docs/src/main/paradox/security/2017.md
deleted file mode 100644
index 5c5ccf29b..000000000
--- a/docs/src/main/paradox/security/2017.md
+++ /dev/null
@@ -1,10 +0,0 @@
-# 2017
-
-@@ toc
-
-@@@ index
-
- * [Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service](2017-05-03-illegal-media-range-in-accept-header-causes-stackoverflowerror.md)
- * [Denial-of-Service by stream leak on unconsumed closed connections](2017-01-23-denial-of-service-via-leak-on-unconsumed-closed-connections.md)
-
-@@@
\ No newline at end of file
diff --git a/docs/src/main/paradox/security/2018-09-05-denial-of-service-via-decodeRequest.md b/docs/src/main/paradox/security/2018-09-05-denial-of-service-via-decodeRequest.md
deleted file mode 100644
index 8c889fe82..000000000
--- a/docs/src/main/paradox/security/2018-09-05-denial-of-service-via-decodeRequest.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# CVE-2018-16131: Denial of Service via unlimited decoding with decodeRequest directive ("zip bomb")
-
-## Date
-
-2018-09-05
-
-## Description
-
-Directives `decodeRequest` and `decodeRequestWith` which handle compressed request data did not limit the amount of uncompressed
-data flowing out of it. In combination with common request directives like `entity(as)`, `toStrict`, or `formField`, this can lead
-to excessive memory usage ultimately leading to an out of memory situation when highly compressed data is received
-(so-called "Zip Bomb").
-
-Any code that uses `decodeRequest` or `decodeRequestWith` is likely to be affected.
-
-## Severity
-
-The CVSS score of this vulnerability is 7.3 (High), based on vector
-[AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:H/RL:W/RC:C](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:H/RL:W/RC:C).
-
-Rationale for the score:
-
- * A:H: Server runs into OOM, so availability is highly affected.
- * E:H: It's relatively simple to exploit.
-
-## Affected Versions
-
-All previously released Akka HTTP versions are affected:
-
- * `10.1.x` versions prior to `10.1.5`
- * `10.0.x` versions prior to `10.0.14`
- * Earlier end-of-lifed versions
-
-Not affected:
-
- * Play and Lagom applications, even though both are using Akka HTTP as their server backend,
- remain unaffected by this vulnerability. This is because they implement their own content
- length validations on top of the underlying models (by using `BodyParser`s).
-
-## Fixed Versions
-
- * 10.1.5
- * 10.0.14
diff --git a/docs/src/main/paradox/security/2018.md b/docs/src/main/paradox/security/2018.md
deleted file mode 100644
index 5fd421f0f..000000000
--- a/docs/src/main/paradox/security/2018.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# 2018
-
-@@ toc
-
-@@@ index
-
- * [Denial of Service via unlimited decoding with decodeRequest directive ("zip bomb")](2018-09-05-denial-of-service-via-decodeRequest.md)
-
-@@@
\ No newline at end of file
diff --git a/docs/src/main/paradox/security/2021-02-24-incorrect-handling-of-Transfer-Encoding-header.md b/docs/src/main/paradox/security/2021-02-24-incorrect-handling-of-Transfer-Encoding-header.md
deleted file mode 100644
index 058f40d8d..000000000
--- a/docs/src/main/paradox/security/2021-02-24-incorrect-handling-of-Transfer-Encoding-header.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# Incorrect Handling Of Transfer-Encoding Header
-
-## Date
-
-24 February 2021
-
-## Description of Vulnerability
-
-HTTP/1.1 defines rules which `Transfer-Encoding` headers are valid and how they should be interpreted. In particular, a `Transfer-Encoding: chunked` header and a `Content-Length` header
-are not allowed to appear in a single message at the same time. This is important to unambiguously delimit subsequent HTTP messages on a connection.
-
-In theory, HTTP/1.1 allows multiple encodings, although, in practice, only `chunked` is relevant. In the case that multiple encodings are present,
-vulnerable versions of Akka HTTP do not correctly validate the rules of the specification and effectively ignore the `Transfer-Encoding` header, use
-a `Content-Length` header if present for delimiting a message, and pass the message to the user unchanged.
-
-If users used Akka HTTP as a reverse proxy, such a message might be forwarded to a backend server. This can potentially lead to "Request Smuggling" if the backend server has a similar but
-different interpretation for that (invalid) set of headers.
-
-## Severity
-
-Based on our assessment, the CVSS score of this vulnerability is 4.2 (Medium), based on vector [(AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:U/RL:O/RC:C)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:U/RL:O/RC:C&version=3.1).
-
-## Impact
-
-A vulnerable Akka HTTP server will accept a malformed message as described above and hand it over to the user. If the user application proxies this message to another server unchanged
-and that server also accepts that message but interprets it as two HTTP messages, the second message has reached the second server without having been inspected by the proxy.
-
-Note that Akka HTTP itself currently does not provide functionality to proxy requests to other servers (but it's easy to build).
-
-In summary, these conditions must be true for an application to be vulnerable:
-
- * use a vulnerable version of Akka HTTP
- * the application must proxy requests to a backend server
- * the backend server must have another bug that accepts the message and interprets the malformed message as two messages
-
-## Resolution
-
-Akka HTTP will no longer accept multiple encodings in `Transfer-Encoding` but only a single `chunked` encoding is valid. HTTP message carrying a combination of `Transfer-Encoding` and
-`Content-Length` headers are rejected.
-
-## Affected versions
-
-- akka-http prior to `10.2.4` and `10.1.14`
-
-## Fixed versions
-
-- akka-http `10.2.4`
-- akka-http `10.1.14`
-
-## Acknowledgements
-
-Thanks, Bastian Ike and Sebastian Rose of AOE for bringing this issue to our attention.
-
-## References
-
- * [CVE-2021-23339](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23339)
- * [SNYK-JAVA-COMTYPESAFEAKKA-1075043](https://snyk.io/vuln/SNYK-JAVA-COMTYPESAFEAKKA-1075043)
- * [#3754](https://github.com/akka/akka-http/pull/3754)
diff --git a/docs/src/main/paradox/security/2021-CVE-2021-42697-stack-overflow-parsing-user-agent.md b/docs/src/main/paradox/security/2021-CVE-2021-42697-stack-overflow-parsing-user-agent.md
deleted file mode 100644
index e6bd682ed..000000000
--- a/docs/src/main/paradox/security/2021-CVE-2021-42697-stack-overflow-parsing-user-agent.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# CVE-2021-42697: Stack overflow while parsing User-Agent header with deeply nested comments
-
-## Date
-
-2021-11-02
-
-## CVE
-
-CVE-2021-42697
-
-## Description of Vulnerability
-
-The HTTP specification [allows arbitrary nesting](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6)
-of `comment` elements in `User-Agent` and other headers. While parsing a request containing a `User-Agent`
-header with deeply nested comments, Akka HTTP may fail with a stack overflow in the parser. Stack overflows
-are handled as fatal errors in Akka leading to a complete shutdown of the application.
-
-## Severity
-
-Based on our assessment, the CVSS score of this vulnerability is 6.7, based on vector [(AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C&version=3.1).
-
-## Impact
-
-An Akka HTTP application server which is exposed to the internet can be remotely crashed
-by sending a crafted `User-Agent` header leading to a loss of availability.
-
-## Resolution
-
-Starting from Akka HTTP 10.2.7, parsing of nested comments will be limited to a configurable maximum depth.
-See `akka.http.parsing.max-comment-parsing-depth` in the @ref:[configuration](../configuration.md) for
-more information. The default value for that setting is currently conservatively set to `5`.
-
-## Workaround
-
-Set `akka.http.server.parsing.modeled-header-parsing = off` to avoid parsing headers to models.
-In this case, Akka HTTP will report most headers as `RawHeader`s. This will likely have
-consequences for downstream user code which expects headers to be already parsed.
-
-## Affected versions
-
-- All akka-http versions prior to `10.2.6`
-
-## Fixed versions
-
-- akka-http `10.2.7`, `10.1.15`
-
-## Acknowledgements
-
-Thanks, Simone Quatrini of SureCloud, for bringing this issue to our attention.
-
-## References
-
-* [#3918](https://github.com/akka/akka-http/issues/3918)
diff --git a/docs/src/main/paradox/security/2021.md b/docs/src/main/paradox/security/2021.md
deleted file mode 100644
index 0b59653a3..000000000
--- a/docs/src/main/paradox/security/2021.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# 2021
-
-@@ toc
-
-@@@ index
-* [Stack overflow while parsing User-Agent header with deeply nested comments](2021-CVE-2021-42697-stack-overflow-parsing-user-agent.md)
-* [Incorrect handling of Transfer-Encoding header](2021-02-24-incorrect-handling-of-Transfer-Encoding-header.md)
-
-@@@
\ No newline at end of file
diff --git a/docs/src/main/paradox/server-side/graceful-termination.md b/docs/src/main/paradox/server-side/graceful-termination.md
index d0fd02ede..64593474f 100644
--- a/docs/src/main/paradox/server-side/graceful-termination.md
+++ b/docs/src/main/paradox/server-side/graceful-termination.md
@@ -1,17 +1,17 @@
# Graceful termination
-## Akka Coordinated Shutdown
+## Pekko Coordinated Shutdown
-@extref[Coordinated shutdown](akka-docs:coordinated-shutdown.html) is Akka's managed way of shutting down multiple modules / sub-systems (persistence, cluster, http etc)
-in a predictable and ordered fashion. For example, in a typical Akka application you will want to stop accepting new HTTP connections, and then shut down the cluster etc.
+@extref[Coordinated shutdown](pekko-docs:coordinated-shutdown.html) is Apache Pekko's managed way of shutting down multiple modules / sub-systems (persistence, cluster, http etc)
+in a predictable and ordered fashion. For example, in a typical Apache Pekko application you will want to stop accepting new HTTP connections, and then shut down the cluster etc.
-The recommended Akka HTTP server shutdown consists of three steps:
+The recommended Apache Pekko HTTP server shutdown consists of three steps:
1. stop accepting new connections (@scala[@scaladoc[ServerBinding.unbind](akka.http.scaladsl.Http.ServerBinding)]@java[@javadoc[ServerBinding.unbind](akka.http.javadsl.ServerBinding)])
1. try to finish handling of ongoing requests until the `hardTerminationDeadline` hits (see below for details)
1. close open connections (@scala[@scaladoc[ServerBinding.terminate](akka.http.scaladsl.Http.ServerBinding)]@java[@javadoc[ServerBinding.terminate](akka.http.javadsl.ServerBinding)])
-This recommended sequence can be added to Akka's coordinated shutdown via @scala[@scaladoc[ServerBinding.addToCoordinatedShutdown](akka.http.scaladsl.Http.ServerBinding)]@java[@javadoc[ServerBinding.addToCoordinatedShutdown](akka.http.javadsl.ServerBinding)] like this:
+This recommended sequence can be added to Pekko's coordinated shutdown via @scala[@scaladoc[ServerBinding.addToCoordinatedShutdown](akka.http.scaladsl.Http.ServerBinding)]@java[@javadoc[ServerBinding.addToCoordinatedShutdown](akka.http.javadsl.ServerBinding)] like this:
Scala
: @@snip[snip](/docs/src/test/scala/docs/http/scaladsl/server/ServerShutdownExampleSpec.scala) { #suggested }
@@ -19,7 +19,7 @@ Scala
Java
: @@snip[snip](/docs/src/test/java/docs/http/javadsl/server/ServerShutdownExampleTest.java) { #suggested }
-You may initiate the Akka shutdown via `ActorSystem.terminate()`, or @scala[`run`] @java[`runAll`] on the `CoordinatedShutdown` extension and pass it a class implementing @apidoc[CoordinatedShutdown.Reason] for informational purposes
+You may initiate the Pekko shutdown via `ActorSystem.terminate()`, or @scala[`run`] @java[`runAll`] on the `CoordinatedShutdown` extension and pass it a class implementing @apidoc[CoordinatedShutdown.Reason] for informational purposes
Scala
: @@snip[snip](/docs/src/test/scala/docs/http/scaladsl/server/ServerShutdownExampleSpec.scala) { #shutdown }
@@ -30,7 +30,7 @@ Java
## Graceful termination using `ServerTerminator`
-Akka HTTP provides two APIs to "stop" the server, either of them are available via the
+Apache Pekko HTTP provides two APIs to "stop" the server, either of them are available via the
@java[@javadoc[ServerBinding](akka.http.javadsl.ServerBinding)]
@scala[@scaladoc[ServerBinding](akka.http.scaladsl.Http$$ServerBinding)]
obtained from starting the server (by using any of the `bind...` methods on the
@@ -42,7 +42,7 @@ It only unbinds the port on which the http server has been listening. This allow
responses that might be still in flight and eventually terminate the entire system. If your application uses long-lived
connections, this does mean that these can delay the termination of your system indefinitely.
-A better and more graceful solution to terminate an Akka HTTP server is to use the
+A better and more graceful solution to terminate an Apache Pekko HTTP server is to use the
@java[@javadoc[ServerBinding.terminate(Duration)](akka.http.javadsl.ServerBinding#terminate-java.time.Duration-)]
@scala[@scaladoc[ServerBinding.terminate(FiniteDuration)](akka.http.scaladsl.Http$$ServerBinding#terminate%28FiniteDuration%29:Future[HttpTerminated])]
method, which not only performs the unbinding, but also
@@ -56,7 +56,7 @@ Immediately the
@scala[@scaladoc[ServerBinding#whenTerminationSignalIssued](akka.http.scaladsl.Http$$ServerBinding#whenTerminationSignalIssued:Future[Deadline]) `Future`]
is completed.
This can be used to signal parts of the application that the HTTP server is shutting down and they should clean up as well.
-Note also that for more advanced shut down scenarios you may want to use the @extref[Coordinated Shutdown](akka-docs:/actors.html#coordinated-shutdown) capabilities of Akka.
+Note also that for more advanced shut down scenarios you may want to use the @extref[Coordinated Shutdown](pekko-docs:/actors.html#coordinated-shutdown) capabilities of Apache Pekko.
Next, all in flight requests will be handled. If a request is "in-flight" (being handled by user code), it is given `hardDeadline` time to complete.
diff --git a/docs/src/main/paradox/server-side/http2.md b/docs/src/main/paradox/server-side/http2.md
index 55e790cd4..0a95f14b8 100644
--- a/docs/src/main/paradox/server-side/http2.md
+++ b/docs/src/main/paradox/server-side/http2.md
@@ -79,7 +79,7 @@ support.
Like in the [HTTP/1.1 'Chunked' transfer encoding](https://datatracker.ietf.org/doc/html/rfc7230#section-4.1.2),
HTTP/2 supports a [trailer part](https://httpwg.org/specs/rfc7540.html#rfc.section.8.1) containing headers
-after the body. Akka HTTP currently doesn't expose the trailing headers of the request. For the response, you
+after the body. Apache Pekko HTTP currently doesn't expose the trailing headers of the request. For the response, you
can either model the trailing headers as the @scala[@scaladoc[HttpEntity.LastChunk](akka.http.scaladsl.model.HttpEntity.LastChunk)]@java[last chunk]
of a @scala[@scaladoc[HttpEntity.Chunked](akka.http.scaladsl.model.HttpEntity.Chunked)]@java[chunked] response entity, or use the
@apidoc[trailer](AttributeKeys$) attribute:
diff --git a/docs/src/main/paradox/server-side/index.md b/docs/src/main/paradox/server-side/index.md
index ede64add5..0438515d4 100644
--- a/docs/src/main/paradox/server-side/index.md
+++ b/docs/src/main/paradox/server-side/index.md
@@ -1,7 +1,7 @@
# 4. Server API
-Akka HTTP also provides an embedded,
-[Reactive-Streams](https://www.reactive-streams.org/)-based, fully asynchronous HTTP/1.1 server implemented on top of @extref[Streams](akka-docs:stream/index.html).
+Apache Pekko HTTP also provides an embedded,
+[Reactive-Streams](https://www.reactive-streams.org/)-based, fully asynchronous HTTP/1.1 server implemented on top of @extref[Streams](pekko-docs:stream/index.html).
It supports the following features:
@@ -11,19 +11,19 @@ It supports the following features:
* Optional @ref[SSL/TLS encryption](server-https-support.md)
* Optional support for [HTTP pipelining](https://en.wikipedia.org/wiki/HTTP_pipelining)
-The server-side components of Akka HTTP are split into two layers:
+The server-side components of Apache Pekko HTTP are split into two layers:
@ref[High-level Server-Side API](../routing-dsl/index.md)
-: Higher-level functionality in the `akka-http` module which offers a very flexible "Routing DSL" for elegantly defining RESTful web services as well as
+: Higher-level functionality in the `pekko-http` module which offers a very flexible "Routing DSL" for elegantly defining RESTful web services as well as
functionality of typical web servers or frameworks, like deconstruction of URIs, content negotiation or static content serving.
@ref[Core Server API](low-level-api.md)
-: The basic low-level server implementation in the `akka-http-core` module.
+: The basic low-level server implementation in the `pekko-http-core` module.
Depending on your needs you can either use the low-level API directly or rely on the high-level
@ref[Routing DSL](../routing-dsl/index.md) which can make the definition of more complex service logic much
easier. You can also interact with different API levels at the same time and, independently of which API level you choose
-Akka HTTP will happily serve many thousand concurrent connections to a single or many clients.
+Apache Pekko HTTP will happily serve many thousand concurrent connections to a single or many clients.
@@@ note
It is recommended to read the @ref[Implications of the streaming nature of Request/Response Entities](../implications-of-streaming-http-entity.md) section,
diff --git a/docs/src/main/paradox/server-side/low-level-api.md b/docs/src/main/paradox/server-side/low-level-api.md
index 2c36c310f..71cbeb45a 100644
--- a/docs/src/main/paradox/server-side/low-level-api.md
+++ b/docs/src/main/paradox/server-side/low-level-api.md
@@ -8,7 +8,7 @@ The core Server API is scoped with a clear focus on the essential functionality
* Response ordering (for transparent pipelining support)
All non-core features of typical HTTP servers (like request routing, file serving, compression, etc.) are left to
-the @ref[higher layers](../routing-dsl/index.md), they are not implemented by the `akka-http-core`-level server itself.
+the @ref[higher layers](../routing-dsl/index.md), they are not implemented by the `pekko-http-core`-level server itself.
Apart from general focus this design keeps the server core small and light-weight as well as easy to understand and
maintain.
@@ -20,21 +20,21 @@ from a background with non-"streaming first" HTTP Servers.
## Streams and HTTP
-The Akka HTTP server is implemented on top of @extref[Streams](akka-docs:stream/index.html) and makes heavy use of it - in its
+The Apache Pekko HTTP server is implemented on top of @extref[Streams](pekko-docs:stream/index.html) and makes heavy use of it - in its
implementation as well as on all levels of its API.
-On the connection level Akka HTTP offers basically the same kind of interface as @extref[Working with streaming IO](akka-docs:stream/stream-io.html):
+On the connection level, Apache Pekko HTTP offers basically the same kind of interface as @extref[Working with streaming IO](pekko-docs:stream/stream-io.html):
A socket binding is represented as a stream of incoming connections. The application pulls connections from this stream
source and, for each of them, provides a @apidoc[Flow[HttpRequest, HttpResponse, \_]] to "translate" requests into responses.
Apart from regarding a socket bound on the server-side as a @apidoc[Source[IncomingConnection, \_]] and each connection as a
@apidoc[Source[HttpRequest, \_]] with a @apidoc[Sink[HttpResponse, \_]] the stream abstraction is also present inside a single HTTP
message: The entities of HTTP requests and responses are generally modeled as a @apidoc[Source[ByteString, \_]]. See also
-the @ref[HTTP Model](../common/http-model.md) for more information on how HTTP messages are represented in Akka HTTP.
+the @ref[HTTP Model](../common/http-model.md) for more information on how HTTP messages are represented in Apache Pekko HTTP.
## Starting and Stopping
-On the most basic level an Akka HTTP server is bound by invoking the `bind` method of the @scala[@scaladoc[akka.http.scaladsl.Http](akka.http.scaladsl.Http$)]@java[@javadoc[akka.http.javadsl.Http](akka.http.javadsl.Http)]
+On the most basic level an Apache Pekko HTTP server is bound by invoking the `bind` method of the @scala[@scaladoc[akka.http.scaladsl.Http](akka.http.scaladsl.Http$)]@java[@javadoc[akka.http.javadsl.Http](akka.http.javadsl.Http)]
extension:
Scala
@@ -81,8 +81,8 @@ Java
: @@snip [HttpServerExampleDocTest.java](/docs/src/test/java/docs/http/javadsl/server/HttpServerExampleDocTest.java) { #full-server-example }
In this example, a request is handled by transforming the request stream with a function @scala[`HttpRequest => HttpResponse`]@java[`Function<HttpRequest, HttpResponse>`]
-using `handleWithSyncHandler` (or equivalently, Akka Stream's `map` operator). Depending on the use case many
-other ways of providing a request handler are conceivable using Akka Stream's combinators.
+using `handleWithSyncHandler` (or equivalently, Apache Pekko Stream's `map` operator). Depending on the use case many
+other ways of providing a request handler are conceivable using Apache Pekko Stream's combinators.
If the application provides a @apidoc[Flow] it is also the responsibility of the application to generate exactly one response
for every request and that the ordering of responses matches the ordering of the associated requests (which is relevant
if HTTP pipelining is enabled where processing of multiple incoming requests may overlap). When relying on
@@ -98,7 +98,7 @@ to deal with streamed entities when receiving a request as well as, in many case
See @ref[HttpEntity](../common/http-model.md#httpentity) for a description of the alternatives.
If you rely on the @ref[Marshalling](../common/marshalling.md) and/or @ref[Unmarshalling](../common/unmarshalling.md) facilities provided by
-Akka HTTP then the conversion of custom types to and from streamed entities can be quite convenient.
+Apache Pekko HTTP then the conversion of custom types to and from streamed entities can be quite convenient.
<a id="http-closing-connection-low-level"></a>
### Closing a connection
@@ -119,7 +119,7 @@ For detailed documentation about configuring and using HTTPS on the server-side
<a id="http-server-layer"></a>
## Stand-Alone HTTP Layer Usage
-Due to its Reactive-Streams-based nature the Akka HTTP layer is fully detachable from the underlying TCP
+Due to its Reactive-Streams-based nature, the Apache Pekko HTTP layer is fully detachable from the underlying TCP
interface. While in most applications this "feature" will not be crucial it can be useful in certain cases to be able
to "run" the HTTP layer (and, potentially, higher-layers) against data that do not come from the network but rather
some other source. Potential scenarios where this might be useful include tests, debugging or low-level event-sourcing
@@ -146,31 +146,31 @@ be materialized once.
Request handling can be parallelized on two axes, by handling several connections in parallel and by
relying on HTTP pipelining to send several requests on one connection without waiting for a response first. In both
-cases the client controls the number of ongoing requests. To prevent being overloaded by too many requests, Akka HTTP
+cases the client controls the number of ongoing requests. To prevent being overloaded by too many requests, Apache Pekko HTTP
can limit the number of requests it handles in parallel.
To limit the number of simultaneously open connections, use the `akka.http.server.max-connections` setting. This setting
applies to all of `Http.bindAndHandle*` methods. If you use `Http.bind`, incoming connections are represented by
-a @apidoc[Source[IncomingConnection, ...]]. Use Akka Stream's combinators to apply backpressure to control the flow of
+a @apidoc[Source[IncomingConnection, ...]]. Use Apache Pekko Stream's combinators to apply backpressure to control the flow of
incoming connections, e.g. by using `throttle` or `mapAsync`.
HTTP pipelining is generally discouraged (and [disabled by most browsers](https://en.wikipedia.org/w/index.php?title=HTTP_pipelining&oldid=700966692#Implementation_in_web_browsers)) but
-is nevertheless fully supported in Akka HTTP. The limit is applied on two levels. First, there's the
+is nevertheless fully supported in Apache Pekko HTTP. The limit is applied on two levels. First, there's the
`akka.http.server.pipelining-limit` config setting which prevents that more than the given number of outstanding requests
is ever given to the user-supplied handler-flow. On the other hand, the handler flow itself can apply any kind of throttling
itself. If you use the `Http.bindAndHandleAsync`
entry-point, you can specify the `parallelism` argument (which defaults to `1`, which means that pipelining is disabled) to control the
number of concurrent requests per connection. If you use `Http.bindAndHandle` or `Http.bind`, the user-supplied handler
flow has full control over how many request it accepts simultaneously by applying backpressure. In this case, you can
-e.g. use Akka Stream's `mapAsync` combinator with a given parallelism to limit the number of concurrently handled requests.
+e.g. use Apache Pekko Stream's `mapAsync` combinator with a given parallelism to limit the number of concurrently handled requests.
Effectively, the more constraining one of these two measures, config setting and manual flow shaping, will determine
how parallel requests on one connection are handled.
<a id="handling-http-server-failures-low-level"></a>
## Handling HTTP Server failures in the Low-Level API
-There are various situations when failure may occur while initialising or running an Akka HTTP server.
-Akka by default will log all these failures, however sometimes one may want to react to failures in addition to them
+There are various situations when failure may occur while initialising or running an Apache Pekko HTTP server.
+Apache Pekko by default will log all these failures, however sometimes one may want to react to failures in addition to them
just being logged, for example by shutting down the actor system, or notifying some external monitoring end-point explicitly.
There are multiple things that can fail when creating and materializing an HTTP Server (similarly, the same applied to
@@ -199,13 +199,13 @@ Java
Once the server has successfully bound to a port, the @apidoc[Source[IncomingConnection, \_]] starts running and emitting
new incoming connections. This source technically can signal a failure as well, however this should only happen in very
dramatic situations such as running out of file descriptors or memory available to the system, such that it's not able
-to accept a new incoming connection. Handling failures in Akka Streams is pretty straight forward, as failures are signaled
+to accept a new incoming connection. Handling failures in Apache Pekko Streams is pretty straight forward, as failures are signaled
through the stream starting from the stage which failed, all the way downstream to the final stages.
#### Connections Source failures
In the example below we add a custom @apidoc[GraphStage] in order to react to the
-stream's failure. See @extref[Custom stream processing](akka-docs:stream/stream-customize.html) for more on custom stages. We signal a `failureMonitor` actor with the cause why the stream is going down, and let the Actor
+stream's failure. See @extref[Custom stream processing](pekko-docs:stream/stream-customize.html) for more on custom stages. We signal a `failureMonitor` actor with the cause why the stream is going down, and let the Actor
handle the rest – maybe it'll decide to restart the server or shutdown the ActorSystem, that however is not our concern anymore.
Scala
@@ -234,7 +234,7 @@ a network failure, it will not be seen as this kind of stream failure. It will i
These failures can be described more or less infrastructure related, they are failing bindings or connections.
-Most of the time you won't need to dive into those very deeply, as Akka will simply log errors of this kind
+Most of the time you won't need to dive into those very deeply, as Apache Pekko will simply log errors of this kind
anyway, which is a reasonable default for such problems.
In order to learn more about handling exceptions in the actual routing layer, which is where your application code
diff --git a/docs/src/main/paradox/server-side/server-https-support.md b/docs/src/main/paradox/server-side/server-https-support.md
index d311043b5..12c6fcf2c 100644
--- a/docs/src/main/paradox/server-side/server-https-support.md
+++ b/docs/src/main/paradox/server-side/server-https-support.md
@@ -1,6 +1,6 @@
# Server HTTPS Support
-Akka HTTP supports TLS encryption on the server-side as well as on the @ref[client-side](../client-side/client-https-support.md).
+Apache Pekko HTTP supports TLS encryption on the server-side as well as on the @ref[client-side](../client-side/client-https-support.md).
The central vehicle for configuring encryption is the @apidoc[HttpsConnectionContext], which can be created using
the static method `ConnectionContext.httpsServer` which is defined like this:
@@ -86,7 +86,7 @@ Oracle in reaction to various security updates and known issues.
We also recommend having a look at the [Play documentation about securing your app](https://www.playframework.com/documentation/2.5.x/ConfiguringHttps#ssl-certificates),
as well as the techniques described in the Play documentation about setting up a [reverse proxy to terminate TLS in
-front of your application](https://www.playframework.com/documentation/2.5.x/HTTPServer) instead of terminating TLS inside the JVM, and therefore Akka HTTP, itself.
+front of your application](https://www.playframework.com/documentation/2.5.x/HTTPServer) instead of terminating TLS inside the JVM, and therefore Apache Pekko HTTP, itself.
Other excellent articles on the subject:
diff --git a/docs/src/main/paradox/server-side/websocket-support.md b/docs/src/main/paradox/server-side/websocket-support.md
index 9532e4cd0..9429c765e 100644
--- a/docs/src/main/paradox/server-side/websocket-support.md
+++ b/docs/src/main/paradox/server-side/websocket-support.md
@@ -3,7 +3,7 @@
WebSocket is a protocol that provides a bi-directional channel between browser and webserver usually run over an
upgraded HTTP(S) connection. Data is exchanged in messages whereby a message can either be binary data or Unicode text.
-Akka HTTP provides a stream-based implementation of the WebSocket protocol that hides the low-level details of the
+Apache Pekko HTTP provides a stream-based implementation of the WebSocket protocol that hides the low-level details of the
underlying binary framing wire-protocol and provides a simple API to implement services using WebSocket.
## Model
@@ -44,7 +44,7 @@ against remote peers where data is received over a physical network connection.)
For sending data, you can use @scala[`TextMessage.apply(text: String)`]@java[`TextMessage.create(String)`] to create a strict message if the
complete message has already been assembled. Otherwise, use @scala[`TextMessage.apply(textStream: Source[String, \_])`]@java[`TextMessage.create(Source<String, ?>)`]
-to create a streaming message from an Akka Stream source.
+to create a streaming message from an Apache Pekko Stream source.
## Routing support
@@ -82,10 +82,10 @@ To handle websocket requests, you can either use the @apidoc[WebSocketUpgrade] a
use the more high-level @ref[Routing Support](#routing-support) described above.
The entrypoint for the WebSocket API is the @apidoc[WebSocketUpgrade] attribute which is added to a request
-if Akka HTTP encounters a WebSocket upgrade request.
+if Apache Pekko HTTP encounters a WebSocket upgrade request.
The WebSocket specification mandates that details of the WebSocket connection are negotiated by placing special-purpose
-HTTP headers into request and response of the HTTP upgrade. In Akka HTTP these HTTP-level details of the WebSocket
+HTTP headers into request and response of the HTTP upgrade. In Apache Pekko HTTP these HTTP-level details of the WebSocket
handshake are hidden from the application and don't need to be managed manually.
Instead, the @apidoc[WebSocketUpgrade] attribute represents a valid WebSocket upgrade request. An application can detect
@@ -158,9 +158,9 @@ Those are often used as a way to keep otherwise idle connections from being clos
connection remains usable even after no data frames are communicated over a longer period of time. Such heartbeat may be
initiated by either side of the connection, and the choice which side performs the heart beating is use-case dependent.
-This is supported in a transparent way via configuration in Akka HTTP, and you can enable it by setting the:
+This is supported in a transparent way via configuration in Apache Pekko HTTP, and you can enable it by setting the:
`akka.http.server.websocket.periodic-keep-alive-max-idle = 1 second` to a specified max idle timeout. The keep alive triggers
-when no other messages are in-flight during the such configured period. Akka HTTP will then automatically send
+when no other messages are in-flight during the such configured period. Apache Pekko HTTP will then automatically send
a [`Ping` frame](https://tools.ietf.org/html/rfc6455#section-5.5.2) for each of such idle intervals.
By default, the automatic keep-alive feature is disabled.
diff --git a/docs/src/main/paradox/technologies.md b/docs/src/main/paradox/technologies.md
index 41474d200..a6c428cab 100644
--- a/docs/src/main/paradox/technologies.md
+++ b/docs/src/main/paradox/technologies.md
@@ -40,7 +40,7 @@ file uploads and provides a typed model to access details of such a payload.
## Server-sent Events (SSE)
-Server-sent Events (SSE) are supported through marshalling that will provide or consume an (Akka Stream based) stream of
+Server-sent Events (SSE) are supported through marshalling that will provide or consume an (Apache Pekko Stream based) stream of
events. See @ref[SSE Support](common/sse-support.md) for more information.
## JSON
diff --git a/project/ValidatePullRequest.scala b/project/ValidatePullRequest.scala
index 7606ef176..dcce06171 100644
--- a/project/ValidatePullRequest.scala
+++ b/project/ValidatePullRequest.scala
@@ -176,7 +176,8 @@ object ValidatePullRequest extends AutoPlugin {
diffOutput
.map(l => l.trim)
.filter(l =>
- l.startsWith("pekko-") ||
+ l.startsWith("http") ||
+ l.startsWith("parsing") ||
l.startsWith("docs") ||
BuildFilesAndDirectories.exists(l startsWith))
.map(l => l.takeWhile(_ != '/'))
@@ -189,7 +190,9 @@ object ValidatePullRequest extends AutoPlugin {
val dirtyDirectories = statusOutput
.map(l => l.trim.dropWhile(_ != ' ').drop(1))
.map(_.takeWhile(_ != '/'))
- .filter(dir => dir.startsWith("pekko-") || dir.startsWith("docs") || BuildFilesAndDirectories.contains(dir))
+ .filter(dir =>
+ dir.startsWith("http") || dir.startsWith("parsing") || dir.startsWith("docs") ||
+ BuildFilesAndDirectories.contains(dir))
.toSet
log.info(
"Detected uncommitted changes in directories (including in dependency analysis): " + dirtyDirectories.mkString(
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pekko.apache.org
For additional commands, e-mail: commits-help@pekko.apache.org