Release 4.34.0.2

.github/RECIPE_TEMPLATE.md

@@ -5,7 +5,7 @@ Brief overview of the recipe.
 
 ### Gradle setup
 ```groovy
-    implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+    implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
     // include here all of the dependencies that are needed to make the code run
 ```
 

README.md

@@ -186,9 +186,9 @@ To install, add these dependencies to your **Gradle** file:
 
 ```groovy
 dependencies {
-    implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-    implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.1"
-    implementation group: "org.http4k", name: "http4k-client-okhttp", version: "4.34.0.1"
+    implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+    implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.2"
+    implementation group: "org.http4k", name: "http4k-client-okhttp", version: "4.34.0.2"
 }
 ```
 

src/docs/blog/http4k_v4/index.md

@@ -106,7 +106,7 @@ For more docs on how to get it all working, head over to the [docs](/guide/refer
 
 <hr/>
 #### Upgrading & library API changes
-Like the neat little worker bunnies we are, we've also taken the opportunity to clean up the http4k source code. All previously deprecated code has been removed, leaving the codebase nice and tidy. If you are upgrading, the best idea is to first upgrade to the last v3 version (v3.285.2), deal with any existing deprecations in place, then simply upgrade again to v4.34.0.1.
+Like the neat little worker bunnies we are, we've also taken the opportunity to clean up the http4k source code. All previously deprecated code has been removed, leaving the codebase nice and tidy. If you are upgrading, the best idea is to first upgrade to the last v3 version (v3.285.2), deal with any existing deprecations in place, then simply upgrade again to v4.34.0.2.
 
 <hr/>
 #### http4k.org

src/docs/guide/howto/attach_context_to_a_request/index.md

@@ -16,7 +16,7 @@ the shared bag of state for each request, and to remove the state after the requ
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 #### String-based keys [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/attach_context_to_a_request/string_key_example.kt)

src/docs/guide/howto/client_as_a_function/index.md

@@ -6,7 +6,7 @@ This example demonstrates using http4k as a client, to consume HTTP services. A
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 ### Code [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/client_as_a_function/example.kt)

src/docs/guide/howto/configure_an_oauth_server/index.md

@@ -4,8 +4,8 @@ description: Recipe for using http4k to create an authorization server that prov
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-security-oauth", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-security-oauth", version: "4.34.0.2"
 ```
 
 For this example, you need to configure `OAuthServer` instance with the correct implementations of your login pages, generation of authentication codes and access tokens.

src/docs/guide/howto/create_a_custom_json_marshaller/index.md

@@ -4,8 +4,8 @@ description: Recipes for using JSON in http4k applications with a variety of pop
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-format-jackson", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-format-jackson", version: "4.34.0.2"
 ```
 
 ### Custom auto-mapping JSON configurations

src/docs/guide/howto/create_a_distributed_tracing_tree/index.md

@@ -4,7 +4,7 @@ description: Recipes for creating a Distributed Tracing Tree
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 When composing several http4k services together and talking to Fakes representing external systems, we can create a tree of Distributed Trace calls by adding RequestTracing filters to our HTTP services and then tracking these trace calls through Events.

src/docs/guide/howto/create_a_swagger_ui/index.md

@@ -4,7 +4,7 @@ description: Create a Swagger UI for your REST API
 ### Installation (Gradle)
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-contract", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-contract", version: "4.34.0.2"
 ```
 
 ### About

src/docs/guide/howto/customise_a_server_backend/index.md

@@ -8,8 +8,8 @@ Whilst the http4k server modules ship with a sensibly configured standard server
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.2"
 ```
 
 The example below shows a customised Jetty setup which enables HTTPS traffic by reimplementing the `ServerConfig` interface. The idea is that this single class will encapsulate the usage of the Server platform API behind the http4k abstraction and provide a simple way to reuse it across different applications.

src/docs/guide/howto/deploy_webjars/index.md

@@ -4,7 +4,7 @@ description: Recipe for using WebJars with http4k
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 
 // for the example...
 implementation group: "org.webjars", name: "swagger-ui", version: "3.43.0"

src/docs/guide/howto/integrate_with_openapi/index.md

@@ -11,9 +11,9 @@ This contract example shows:
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-contract", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-format-argo", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-contract", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-format-argo", version: "4.34.0.2"
 ```
 
 Note: although we use Argo here as our JSON API, you could also switch in any of the `http4k-format-xxx` JSON modules. 

src/docs/guide/howto/leverage_graphql/index.md

@@ -4,8 +4,8 @@ description: Recipe for using GraphQL plugins
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-graphql", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-graphql", version: "4.34.0.2"
 ```
 
 ### Code [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/leverage_graphql/example.kt)

src/docs/guide/howto/lookup_a_user_principal/index.md

@@ -5,7 +5,7 @@ description: Recipes for looking up and populating a user principal from a reque
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 When authorising requests, it is common to need to store some credentials or a user principal object to be accessible by a further Filter or the eventual HttpHandler.

src/docs/guide/howto/monitor_http4k/index.md

@@ -6,8 +6,8 @@ Measuring performance of application estate is crucial in today's microservice w
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-metrics-micrometer", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-metrics-micrometer", version: "4.34.0.2"
 ```
 
 ### Metrics (Micrometer) [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/monitor_http4k/example_micrometer.kt)

src/docs/guide/howto/moshi_lite/index.md

@@ -15,7 +15,7 @@ But until then, you can use this recipe to take advantage of the performance gai
 This recipe uses the 3rd-party [moshi-metadata-reflect](https://github.com/ZacSweers/MoshiX/tree/main/moshi-metadata-reflect) module.
 
 ```kotlin
-implementation("org.http4k:http4k-format-moshi:4.34.0.1") {
+implementation("org.http4k:http4k-format-moshi:4.34.0.2") {
     exclude("com.squareup.moshi", "moshi-kotlin")
 }
 implementation("dev.zacsweers.moshix:moshi-metadata-reflect:0.19.0")

src/docs/guide/howto/nestable_routes/index.md

@@ -44,7 +44,7 @@ Note that paths, not strings, will match by default. `"/news/{date}"` will match
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 ### Code [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/nestable_routes/example.kt)

src/docs/guide/howto/record_and_replay_http_traffic/index.md

@@ -6,7 +6,7 @@ A set of classes to provide simple recording/replaying of HTTP traffic. This is
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 ### Caching HTTP Traffic 

src/docs/guide/howto/secure_and_auth_http/index.md

@@ -4,10 +4,10 @@ description: Recipes for how to secure and authenticate HTTP services
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 
 // for OAuth examples
-implementation group: "org.http4k", name: "http4k-security-oauth", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-security-oauth", version: "4.34.0.2"
 ```
 
 http4k provides a set of Filters for authenticating into other HTTP services. Usage of these filters is shown below to authenticate into a service. Each authentication type is generally available using both dynamic and static credential provision and checking mechanisms.

src/docs/guide/howto/serve_sse/index.md

@@ -4,8 +4,8 @@ description: Recipes for using http4k with Server-Sent Events
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-server-undertow", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-server-undertow", version: "4.34.0.2"
 ```
 
 **http4k** provides SSE (Server Sent Events) support using a simple, consistent, typesafe, and testable API on supported server backends (see above). SSE communication consists of 3 main concepts:

src/docs/guide/howto/serve_websockets/index.md

@@ -4,10 +4,10 @@ description: Recipes for using http4k with websockets
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-client-websocket", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-format-jackson", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-client-websocket", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-format-jackson", version: "4.34.0.2"
 ```
 
 **http4k** provides Websocket support using a simple, consistent, typesafe, and testable API on supported server backends (see above). Websocket communication consists of 4 main concepts:

src/docs/guide/howto/server_as_a_function/index.md

@@ -6,7 +6,7 @@ This example is the simplest possible "server" implementation. Note that we are
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 ### Code [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/server_as_a_function/example.kt)

src/docs/guide/howto/simple_routing/index.md

@@ -8,7 +8,7 @@ For the typesafe contract-style routing, refer to [this](/guide/howto/integrate_
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 ### Code [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/simple_routing/example.kt)

src/docs/guide/howto/structure_your_logs_with_events/index.md

@@ -4,8 +4,8 @@ description: Recipe for using http4k Events to send structured logs to external
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-format-jackson", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-format-jackson", version: "4.34.0.2"
 ```
 
 In order to leverage modern log aggregation platforms, we should move away from logging arbitrary strings into the StdOut of our applications, and move towards [Structured Logging](https://www.thoughtworks.com/radar/techniques/structured-logging) instead, which allows us to treat logs as data which can be mined to give us better observability of our systems. This also encourages the move for developers to think about which events happening in your apps are actually important and what data is appropriate to be attached to each one.

src/docs/guide/howto/typesafe_your_api_with_lenses/index.md

@@ -6,7 +6,7 @@ Example showing how to create and apply lenses to requests and responses to both
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 ### Standard (exception based) approach [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/typesafe_your_api_with_lenses/example.kt)

src/docs/guide/howto/use_a_custom_oauth_provider/index.md

@@ -6,8 +6,8 @@ It is very easy to configure http4k to integrate with any OAuth2 provider who su
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-security-oauth", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-security-oauth", version: "4.34.0.2"
 ```
 
 For this example, simply reconfigure the `OAuthProvider` instance with the correct details, and provide custom logic for persisting and retrieving the CSRF and AccessToken.

src/docs/guide/howto/use_a_server_backend/index.md

@@ -8,9 +8,9 @@ Alternatively, any http4k application can be mounted into any Servlet container
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-client-apache", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-client-apache", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-server-jetty", version: "4.34.0.2"
 ```
 
 ### Code [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/use_a_server_backend/example.kt)

src/docs/guide/howto/use_a_templating_engine/index.md

@@ -6,8 +6,8 @@ Example showing how to use the Templating modules - in this case Handlebars, bot
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-template-handlebars", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-template-handlebars", version: "4.34.0.2"
 ```
 
 ### Code [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/use_a_templating_engine/example.kt)

src/docs/guide/howto/use_auto_content_negotiation/index.md

@@ -8,13 +8,13 @@ Example showing how to combine multiple body Lenses into a single facade that wi
 Auto Content Negotiation is available in the core http4k module.
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-format-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-format-core", version: "4.34.0.2"
 ```
 
 But it also integrates with the contract module.
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-contract", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-contract", version: "4.34.0.2"
 ```
 
 ### Rationale

src/docs/guide/howto/use_html_forms/index.md

@@ -9,7 +9,7 @@ HTML form support is provided on 2 levels:
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
 ```
 
 ### Standard (non-typesafe) API [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/use_html_forms/example_standard.kt)

src/docs/guide/howto/use_multipart_forms/index.md

@@ -9,8 +9,8 @@ Multipart form support is provided on 2 levels:
 ### Gradle setup
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.1"
-implementation group: "org.http4k", name: "http4k-multipart", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-core", version: "4.34.0.2"
+implementation group: "org.http4k", name: "http4k-multipart", version: "4.34.0.2"
 ```
 
 ### Standard (non-typesafe) API [<img class="octocat"/>](https://github.com/http4k/http4k/blob/master/src/docs/guide/howto/use_multipart_forms/example_standard.kt)

src/docs/guide/reference/approvaltests/index.md

@@ -4,7 +4,7 @@ description: Feature overview of the http4k-testing-approval module
 ### Installation (Gradle)
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-testing-approval", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-testing-approval", version: "4.34.0.2"
 ```
 
 ### About

src/docs/guide/reference/aws/index.md

@@ -4,7 +4,7 @@ description: Feature overview of the http4k-aws module
 ### Installation (Gradle)
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-aws", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-aws", version: "4.34.0.2"
 ```
 
 ### About

src/docs/guide/reference/chaos/index.md

@@ -4,7 +4,7 @@ description: Feature overview of the http4k-testing-chaos module
 ### Installation (Gradle)
 
 ```groovy
-implementation group: "org.http4k", name: "http4k-testing-chaos", version: "4.34.0.1"
+implementation group: "org.http4k", name: "http4k-testing-chaos", version: "4.34.0.2"
 ```
 
 ### About