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/pekko-http.git
The following commit(s) were added to refs/heads/main by this push:
new dfbb8b83e broken migration guide link (#602)
dfbb8b83e is described below
commit dfbb8b83e059aa40e9d342c56410cc835b38de73
Author: PJ Fanning <[email protected]>
AuthorDate: Mon Sep 16 10:32:30 2024 +0100
broken migration guide link (#602)
* broken migration guide link
* Update index.md
* emerose.com offline
* Update index.md
---
docs/src/main/paradox/migration-guide/index.md | 2 +-
.../main/paradox/routing-dsl/directives/security-directives/index.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/src/main/paradox/migration-guide/index.md
b/docs/src/main/paradox/migration-guide/index.md
index 92d5435df..2cd78f2a0 100644
--- a/docs/src/main/paradox/migration-guide/index.md
+++ b/docs/src/main/paradox/migration-guide/index.md
@@ -3,7 +3,7 @@
@@toc { depth=3 }
* 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)
-* The @extref:[migration guide](pekko-docs:project/migration-guides.html) for
the core Apache Pekko libs is a useful guideline.
+* The @extref:[migration guide](pekko-docs:migration/index.html) for the core
Apache Pekko libs is a useful guideline.
* for Pekko jar dependencies, the groupId is "org.apache.pekko" instead of
"com.typesafe.akka"
* the jar names start with "pekko" instead of "akka" - e.g.
pekko-http_2.13.jar instead of akka-http_2.13.jar
* If you have a dependency akka-http2-support, Pekko does not need a separate
jar. The support is built into main pekko-http jars.
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 401f600f7..27c90af0a 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
@@ -62,7 +62,7 @@ as defined in [RFC
6750](https://tools.ietf.org/html/rfc6750), and allow users t
When transforming request `Credentials` into an application specific user
identifier the naive solution for
checking the secret (password) would be a regular string comparison, but doing
this would open up the application to
-timing attacks. See for example [Timing Attacks
Explained](https://emerose.com/timing-attacks-explained) for an explanation of
the problem.
+timing attacks. See for example [Timing Attacks
Explained](https://web.archive.org/web/20230902003704/https://emerose.com/timing-attacks-explained)
for an explanation of the problem.
To protect users of the library from that mistake the secret is not available
through the API, instead the method
`Credentials.Provided.verify(String)` should be used. It does a constant time
comparison rather than returning early
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
