From eadfd822104bdc1d8f0129c3d56ec18f99d8c1e6 Mon Sep 17 00:00:00 2001 From: Enno Runne <458526+ennru@users.noreply.github.com> Date: Fri, 4 Oct 2024 16:09:43 +0200 Subject: [PATCH] Fix more links --- build.sbt | 2 +- .../main/paradox/migration-guide/migration-guide-10.2.x.md | 4 ++-- docs/src/main/paradox/routing-dsl/testkit.md | 2 +- scripts/link-validator.conf | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/build.sbt b/build.sbt index 8efbc765eaa..8386f744732 100644 --- a/build.sbt +++ b/build.sbt @@ -35,7 +35,7 @@ inThisBuild(Def.settings( val tagOrBranch = if (isSnapshot.value) "main" else "v" + version.value - Seq(("BUSL-1.1", url(s"https://raw.githubusercontent.com/akka/akka-http/${tagOrBranch}/LICENSE"))) + Seq(("BUSL-1.1", url(s"https://github.com/akka/akka-http/blob/${tagOrBranch}/LICENSE.txt"))) }, description := "Akka Http: Modern, fast, asynchronous, streaming-first HTTP server and client.", testOptions ++= Seq( 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 index 26472448e35..4df95589c27 100644 --- 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 @@ -89,7 +89,7 @@ agent has been dropped in 10.2.0. HTTP/2 support therefore now requires to be ru 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)). +(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 @@ -222,7 +222,7 @@ 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 +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 diff --git a/docs/src/main/paradox/routing-dsl/testkit.md b/docs/src/main/paradox/routing-dsl/testkit.md index 34eec56b39b..78b24f597b6 100644 --- a/docs/src/main/paradox/routing-dsl/testkit.md +++ b/docs/src/main/paradox/routing-dsl/testkit.md @@ -58,7 +58,7 @@ route structure defined in your service. The final element of the `~>` chain is a `check` call, which takes a block of assertions as parameter. In this block you define your requirements onto the result produced by your route after having processed the given request. Typically you use one of the defined "inspectors" to retrieve a particular element of the routes response and express assertions -against it using the test DSL provided by your test framework. For example, with [scalatest](http://www.scalatest.org), in order to verify that +against it using the test DSL provided by your test framework. For example, with [scalatest](https://www.scalatest.org), in order to verify that your route responds to the request with a status 200 response, you'd use the `status` inspector and express an assertion like this: diff --git a/scripts/link-validator.conf b/scripts/link-validator.conf index f49d595c2e4..1a0027233ad 100644 --- a/scripts/link-validator.conf +++ b/scripts/link-validator.conf @@ -26,7 +26,7 @@ site-link-validator { # MVN repository forbids access after a few requests "https://mvnrepository.com/artifact/" "http://localhost:" - "https://example.com/" + "http://example.com/" ] ignore-files = []