From 73b91b3706c72716139c9a26061e1fe7ed9da8a9 Mon Sep 17 00:00:00 2001 From: daviddenton Date: Thu, 10 Oct 2024 09:50:27 +0000 Subject: [PATCH] deploy: http4k/www@73cdb08be73fbe57a8d79b4d90bfbb032aee8a95 --- 404.html | 2 +- code-of-conduct/index.html | 2 +- community/index.html | 2 +- company/index.html | 2 +- consulting/index.html | 2 +- disclaimer/index.html | 2 +- ecosystem/connect/changelog/index.html | 2 +- ecosystem/connect/concepts/clients/index.html | 2 +- ecosystem/connect/concepts/fakes/index.html | 2 +- ecosystem/connect/concepts/pattern/index.html | 2 +- ecosystem/connect/contributing/index.html | 2 +- ecosystem/connect/index.html | 2 +- ecosystem/connect/reference/ai/anthropic/index.html | 2 +- ecosystem/connect/reference/ai/azure/index.html | 2 +- ecosystem/connect/reference/ai/langchain/index.html | 2 +- ecosystem/connect/reference/ai/lmstudio/index.html | 2 +- ecosystem/connect/reference/ai/ollama/index.html | 2 +- ecosystem/connect/reference/ai/openai/index.html | 2 +- ecosystem/connect/reference/amazon/apprunner/index.html | 2 +- ecosystem/connect/reference/amazon/cloudfront/index.html | 2 +- ecosystem/connect/reference/amazon/cloudwatchlogs/index.html | 2 +- ecosystem/connect/reference/amazon/cognito/index.html | 2 +- .../connect/reference/amazon/containercredentials/index.html | 2 +- ecosystem/connect/reference/amazon/dynamodb/index.html | 2 +- ecosystem/connect/reference/amazon/eventbridge/index.html | 2 +- ecosystem/connect/reference/amazon/evidently/index.html | 2 +- ecosystem/connect/reference/amazon/firehose/index.html | 2 +- ecosystem/connect/reference/amazon/iamidentitycenter/index.html | 2 +- ecosystem/connect/reference/amazon/instancemetadata/index.html | 2 +- ecosystem/connect/reference/amazon/kms/index.html | 2 +- ecosystem/connect/reference/amazon/lambda/index.html | 2 +- ecosystem/connect/reference/amazon/s3/index.html | 2 +- ecosystem/connect/reference/amazon/secretsmanager/index.html | 2 +- ecosystem/connect/reference/amazon/ses/index.html | 2 +- ecosystem/connect/reference/amazon/sns/index.html | 2 +- ecosystem/connect/reference/amazon/sqs/index.html | 2 +- ecosystem/connect/reference/amazon/sts/index.html | 2 +- ecosystem/connect/reference/amazon/systemsmanager/index.html | 2 +- ecosystem/connect/reference/aws/index.html | 2 +- ecosystem/connect/reference/github/index.html | 2 +- ecosystem/connect/reference/gitlab/index.html | 2 +- ecosystem/connect/reference/google/analytics-ga4/index.html | 2 +- ecosystem/connect/reference/google/analytics-ua/index.html | 2 +- ecosystem/connect/reference/kafka/rest/index.html | 2 +- ecosystem/connect/reference/kafka/schemaregistry/index.html | 2 +- ecosystem/connect/reference/ksp/index.html | 2 +- ecosystem/connect/reference/mattermost/index.html | 2 +- ecosystem/connect/reference/overview/index.html | 2 +- ecosystem/connect/reference/storage/core/index.html | 2 +- ecosystem/connect/reference/storage/http/index.html | 2 +- ecosystem/connect/reference/storage/jdbc/index.html | 2 +- ecosystem/connect/reference/storage/redis/index.html | 2 +- ecosystem/connect/reference/storage/s3/index.html | 2 +- ecosystem/http4k-connect/index.html | 2 +- ecosystem/http4k-core/index.html | 2 +- ecosystem/http4k/changelog/index.html | 2 +- ecosystem/http4k/concepts/http/index.html | 2 +- ecosystem/http4k/concepts/lens/index.html | 2 +- ecosystem/http4k/concepts/server-sent-events/index.html | 2 +- ecosystem/http4k/concepts/serverless/index.html | 2 +- ecosystem/http4k/concepts/websockets/index.html | 2 +- ecosystem/http4k/contributing/index.html | 2 +- ecosystem/http4k/index.html | 2 +- ecosystem/http4k/reference/approvaltests/index.html | 2 +- ecosystem/http4k/reference/aws/index.html | 2 +- ecosystem/http4k/reference/azure/index.html | 2 +- ecosystem/http4k/reference/chaos/index.html | 2 +- ecosystem/http4k/reference/clients/index.html | 2 +- ecosystem/http4k/reference/cloud_events/index.html | 2 +- ecosystem/http4k/reference/cloud_native/index.html | 2 +- ecosystem/http4k/reference/config/index.html | 2 +- ecosystem/http4k/reference/contracts/index.html | 2 +- ecosystem/http4k/reference/core/index.html | 2 +- ecosystem/http4k/reference/dataframe/index.html | 2 +- ecosystem/http4k/reference/digest/index.html | 2 +- ecosystem/http4k/reference/failsafe/index.html | 2 +- ecosystem/http4k/reference/graphql/index.html | 2 +- ecosystem/http4k/reference/hamkrest/index.html | 2 +- ecosystem/http4k/reference/htmx/index.html | 2 +- ecosystem/http4k/reference/index.html | 2 +- ecosystem/http4k/reference/json/index.html | 2 +- ecosystem/http4k/reference/jsonrpc/index.html | 2 +- ecosystem/http4k/reference/kotest/index.html | 2 +- ecosystem/http4k/reference/micrometer/index.html | 2 +- ecosystem/http4k/reference/multipart/index.html | 2 +- ecosystem/http4k/reference/oauth/index.html | 2 +- ecosystem/http4k/reference/opentelemetry/index.html | 2 +- ecosystem/http4k/reference/playwright/index.html | 2 +- ecosystem/http4k/reference/resilience4j/index.html | 2 +- ecosystem/http4k/reference/serverless/index.html | 2 +- ecosystem/http4k/reference/servers/index.html | 2 +- ecosystem/http4k/reference/servicevirtualisation/index.html | 2 +- ecosystem/http4k/reference/strikt/index.html | 2 +- ecosystem/http4k/reference/templating/index.html | 2 +- ecosystem/http4k/reference/testing/index.html | 2 +- ecosystem/http4k/reference/tracerbullet/index.html | 2 +- ecosystem/http4k/reference/webdriver/index.html | 2 +- ecosystem/http4k/reference/webhooks/index.html | 2 +- ecosystem/http4k/reference/xml/index.html | 2 +- ecosystem/http4k/reference/yaml/index.html | 2 +- ecosystem/index.html | 2 +- faq/index.html | 2 +- howto/arrange_filters_into_stacks/index.html | 2 +- howto/attach_context_to_a_request/index.html | 2 +- howto/client_as_a_function/index.html | 2 +- howto/configure_an_oauth_server/index.html | 2 +- howto/create_a_custom_json_marshaller/index.html | 2 +- howto/create_a_swagger_ui/index.html | 2 +- howto/customise_a_server_backend/index.html | 2 +- howto/deploy_webjars/index.html | 2 +- howto/implement-your-own-clients/index.html | 2 +- howto/index.html | 2 +- howto/integrate_with_openapi/index.html | 2 +- howto/leverage_graphql/index.html | 2 +- howto/lookup_a_user_principal/index.html | 2 +- howto/make_json_faster/index.html | 2 +- howto/make_parallel_calls/index.html | 2 +- howto/monitor_http4k/index.html | 2 +- howto/nestable_routes/index.html | 2 +- howto/pimp-your-clients-with-ksp/index.html | 2 +- howto/record_and_replay_http_traffic/index.html | 2 +- howto/secure_and_auth_http/index.html | 2 +- howto/self_document_systems_with_tests/index.html | 2 +- howto/serve_sse/index.html | 2 +- howto/serve_websockets/index.html | 2 +- howto/server_as_a_function/index.html | 2 +- howto/simple_routing/index.html | 2 +- howto/structure_your_logs_with_events/index.html | 2 +- howto/test_using_service_virtualisation/index.html | 2 +- howto/typesafe_your_api_with_lenses/index.html | 2 +- howto/use_a_custom_oauth_provider/index.html | 2 +- howto/use_a_server_backend/index.html | 2 +- howto/use_a_templating_engine/index.html | 2 +- howto/use_auto_content_negotiation/index.html | 2 +- howto/use_html_forms/index.html | 2 +- howto/use_multipart_forms/index.html | 2 +- howto/write_different_test_types/index.html | 2 +- index.html | 2 +- learn/index.html | 2 +- lts-support/index.html | 2 +- module/index.html | 2 +- news/documenting_apis_with_openapi/index.html | 2 +- news/http4k_v4/index.html | 2 +- news/http4k_v5/index.html | 2 +- news/index.html | 2 +- news/meet_http4k/index.html | 2 +- news/nanoservices/index.html | 2 +- news/regarding_jcenter/index.html | 2 +- news/retrospective_v3/index.html | 2 +- news/toolbox/index.html | 2 +- news/typesafe_configuration/index.html | 2 +- news/typesafe_websockets/index.html | 2 +- overview/index.html | 2 +- performance/index.html | 2 +- privacy-policy/index.html | 2 +- quickstart/index.html | 2 +- rationale/index.html | 2 +- security-policy/index.html | 2 +- security/index.html | 2 +- showcase/index.html | 2 +- solutions/index.html | 2 +- terms-and-conditions/index.html | 2 +- training/index.html | 2 +- tutorial/going_native_with_graal_on_aws_lambda/index.html | 2 +- tutorial/index.html | 2 +- tutorial/serverless_http4k_with_aws_lambda/index.html | 2 +- tutorial/tdding_http4k/index.html | 2 +- tutorial/tdding_http4k/part1/index.html | 2 +- tutorial/tdding_http4k/part2/index.html | 2 +- tutorial/tdding_http4k/part3/index.html | 2 +- tutorial/tdding_http4k/part4/index.html | 2 +- tutorial/your_first_http4k_app/index.html | 2 +- 172 files changed, 172 insertions(+), 172 deletions(-) diff --git a/404.html b/404.html index 2f139a635..5c0c4802b 100644 --- a/404.html +++ b/404.html @@ -76,4 +76,4 @@ 404 \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/code-of-conduct/index.html b/code-of-conduct/index.html index 49a1d4e94..ee312a59b 100644 --- a/code-of-conduct/index.html +++ b/code-of-conduct/index.html @@ -123,4 +123,4 @@ https://www.contributor-covenant.org/translations.

pumb
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/community/index.html b/community/index.html index 6cbea2ea3..2d271d8dd 100644 --- a/community/index.html +++ b/community/index.html @@ -75,4 +75,4 @@

Our Community of Contributors

The http4k ecosystem, like much of the Open Source world, thrives thanks to the collective effort of individuals and companies who generously offer their time, expertise, and resources. Every contributor, whether through code, documentation, testing, or financial support, plays a critical role in shaping this project.

We owe a debt of gratitude to all those who have shared their knowledge, identified bugs, suggested features, and helped maintain the high standards of http4k. Your contributions are the foundation upon which this project grows, allowing developers across the globe to benefit from a robust and evolving toolset.

To everyone who has supported http4k in any form, we extend our heartfelt thanks for being a part of this journey and helping us continue building for the future of Open Source.

Contributors

Thank you to all the people who have contributed to the http4k ecosystem!

logo

Vendor Support

IntelliJ from Jetbrains

Jetbrains kindly provides the project with an Open Source License for the amazing IntelliJ IDE and their suite of developer productivity tools.

logo

Tuple from Tuple

Tuple provides the http4k team with their amazing Pair-Programming tool Tuple allowing us to collaborate to build the library.

logo

JProfiler from YourKit

YourKit supports open source projects with innovative and intelligent tools for monitoring and profiling .Net and Java applications.

logo
pumb
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/company/index.html b/company/index.html index 9dd37efba..f90282ca8 100644 --- a/company/index.html +++ b/company/index.html @@ -84,4 +84,4 @@ on innovative projects, we’d love to hear from you!

Professional Services

support

Support

It’s important that you can rely on your core dependencies for the long term. That’s why we offer Long Term Support packages (LTS) for http4k releases.

Safeguard your projects
faq

Solve

We’ve designed http4k to be simple to work with, but getting professional advice about effectively using it from specialist experts can 🚀 your projects.

Unlock peak performance
training

Educate

We provide hands-on training to help you get the most out of http4k. You can get help from the creators of http4k to learn how to use it effectively.

Level up your team

Let's talk

Contact us
pumb
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/consulting/index.html b/consulting/index.html index ee9398dd3..7a5885399 100644 --- a/consulting/index.html +++ b/consulting/index.html @@ -75,4 +75,4 @@

Consulting

Unlock the full potential of your applications with consulting services directly from the architects of http4k. We provide tailored guidance and support at every stage of your journey through the http4k ecosystem.

We recognise that although organisations use happily Open Source Software such as http4k, they may gain additional peace of mind from having direct access to expert advice. For this purpose, the project creators offer a range of professional services to support http4k users in making the most of the powerful feature set which http4k provides, including:

  • System architecture and design review
  • Testing strategy and implementation review
  • Project-level Developer and Team mentoring
  • Troubleshooting integration issues and debugging
  • Kotlin language Developer training
  • Advice on extending or creating custom builds of http4k

If your organisation is interested in getting support or consulting on this basis, please get in touch.

Contact us

Custom consulting from the experts

No-one knows http4k better than the people who built it. Get tailored advice and support from the creators of http4k.

System architecture and design review

Get expert advice on how to structure your applications for maximum performance and maintainability.

Troubleshooting and debugging

If you’re having problems with your http4k application, we can help you get to the bottom of it.

Professional Services

Support

It’s important that you can rely on your core dependencies for the long term. That’s why we offer Long Term Support packages (LTS) for http4k releases.

Safeguard your projects

Solve

We’ve designed http4k to be simple to work with, but getting professional advice about effectively using it from specialist experts can 🚀 your projects.

Unlock peak performance

Educate

We provide hands-on training to help you get the most out of http4k. You can get help from the creators of http4k to learn how to use it effectively.

Level up your team

Let's talk

Contact us
pumb
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/disclaimer/index.html b/disclaimer/index.html index 1d7eb307a..22179c7e0 100644 --- a/disclaimer/index.html +++ b/disclaimer/index.html @@ -75,4 +75,4 @@

Disclaimer

Last updated: 2024-05-20

WEBSITE DISCLAIMER

The information provided by http4k Ltd (“Company”, “we”, “our”, “us”) on http4k.org (the “Site”) is for general informational purposes only. All information on the Site is provided in good faith, however we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the Site.

UNDER NO CIRCUMSTANCE SHALL WE HAVE ANY LIABILITY TO YOU FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF THE SITE OR RELIANCE ON ANY INFORMATION PROVIDED ON THE SITE. YOUR USE OF THE SITE AND YOUR RELIANCE ON ANY INFORMATION ON THE SITE IS SOLELY AT YOUR OWN RISK.

EXTERNAL LINKS DISCLAIMER

The Site may contain (or you may be sent through the Site) links to other websites or content belonging to or originating from third parties or links to websites and features. Such external links are not investigated, monitored, or checked for accuracy, adequacy, validity, reliability, availability or completeness by us.

WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR THE ACCURACY OR RELIABILITY OF ANY INFORMATION OFFERED BY THIRD-PARTY WEBSITES LINKED THROUGH THE SITE OR ANY WEBSITE OR FEATURE LINKED IN ANY BANNER OR OTHER ADVERTISING. WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES.

AFFILIATES DISCLAIMER

The Site may contain links to affiliate websites, and we may receive an affiliate commission for any purchases or actions made by you on the affiliate websites using such links.

TESTIMONIALS DISCLAIMER

The Site may contain testimonials by users of our products and/or services. These testimonials reflect the real-life experiences and opinions of such users. However, the experiences are personal to those particular users, and may not necessarily be representative of all users of our products and/or services. We do not claim, and you should not assume that all users will have the same experiences.

YOUR INDIVIDUAL RESULTS MAY VARY.

The testimonials on the Site are submitted in various forms such as text, audio and/or video, and are reviewed by us before being posted. They appear on the Site verbatim as given by the users, except for the correction of grammar or typing errors. Some testimonials may have been shortened for the sake of brevity, where the full testimonial contained extraneous information not relevant to the general public.

The views and opinions contained in the testimonials belong solely to the individual user and do not reflect our views and opinions.

ERRORS AND OMISSIONS DISCLAIMER

While we have made every attempt to ensure that the information contained in this site has been obtained from reliable sources, http4k Ltd is not responsible for any errors or omissions or for the results obtained from the use of this information. All information in this site is provided “as is”, with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information, and without warranty of any kind, express or implied, including, but not limited to warranties of performance, merchantability, and fitness for a particular purpose.

In no event will http4k Ltd, its related partnerships or corporations, or the partners, agents or employees thereof be liable to you or anyone else for any decision made or action taken in reliance on the information in this Site or for any consequential, special or similar damages, even if advised of the possibility of such damages.

LOGOS AND TRADEMARKS DISCLAIMER

All logos and trademarks of third parties referenced on http4k.org are the trademarks and logos of their respective owners. Any inclusion of such trademarks or logos does not imply or constitute any approval, endorsement or sponsorship of http4k Ltd by such owners.

CONTACT US

Should you have any feedback, comments, requests for technical support or other inquiries, please contact us by email: info@http4k.org.

pumb
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/changelog/index.html b/ecosystem/connect/changelog/index.html index 3d6496215..cc8c160ad 100644 --- a/ecosystem/connect/changelog/index.html +++ b/ecosystem/connect/changelog/index.html @@ -88,4 +88,4 @@

v2.13.0.1

v2.13.0.0

v2.12.0.0

v2.11.0.0

v2.10.0.0

v2.9.2.0

v2.9.1.0

v2.9.0.0

v2.8.0.0

v2.7.1.0

v2.7.0.0

v2.6.0.0

v2.5.1.0

v2.5.0.0

v2.4.0.0

v2.3.2.0

v2.3.1.1

v2.3.1.0

v2.3.0.0

v2.2.2.0

v2.2.1.0

v2.2.0.0

v2.1.0.0

v2.0.2.1

v1.1.0.1

v1.0.1.0

v1.0.0.0

v0.20.0.0

\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/concepts/clients/index.html b/ecosystem/connect/concepts/clients/index.html index 3145c5c80..b6ef6a775 100644 --- a/ecosystem/connect/concepts/clients/index.html +++ b/ecosystem/connect/concepts/clients/index.html @@ -95,4 +95,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/concepts/fakes/index.html b/ecosystem/connect/concepts/fakes/index.html index cd9e0c655..792534044 100644 --- a/ecosystem/connect/concepts/fakes/index.html +++ b/ecosystem/connect/concepts/fakes/index.html @@ -77,4 +77,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/concepts/pattern/index.html b/ecosystem/connect/concepts/pattern/index.html index 9dc4c6479..c28ce38f2 100644 --- a/ecosystem/connect/concepts/pattern/index.html +++ b/ecosystem/connect/concepts/pattern/index.html @@ -261,4 +261,4 @@

Summary

Actions and API Clients are the core building blocks of http4k Connect. They allow us to structure our API Client code in a modular, testable and reusable way, and also to compose our own custom API Clients out of the individual parts that we are interested in. The Connect pattern is a powerful way to structure our API Client code in a way that is similar to how we structure our inbound APIs, and also to build functions which combine one or more calls to the API.

\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/contributing/index.html b/ecosystem/connect/contributing/index.html index 8c76b4701..3c9db35fc 100644 --- a/ecosystem/connect/contributing/index.html +++ b/ecosystem/connect/contributing/index.html @@ -75,4 +75,4 @@

Contributors Guide

Contributions

Notes for adding a new Client & Fake

  • Use the Example project client and fake as a template module.
  • The naming of the modules is: http4k-connect-<vendor>-<system>. We are also grouping the systems by vendor in directory structure. To add the modules in the right place in settings.gradle.kts use the functions provided.
  • The work for adding other http4k-connect Gradle dependencies is already done in the core build.gradle file. You just need to add external dependencies into the module gradle file if there are any. If not, feel free to omit it.
  • Fakes should extend ChaoticHttpHandler, which adds in the misbehave() and behave() functions to enable the Chaotic behaviour.
  • Each Fake should implement the FakeSystemContract.
  • Tests against external systems should be added wherever possible to prove the contracts are in place, or adding Docker* setup to run them. *This is work in progress.

Notes for adding Storage implementations

  • The naming of the modules is: http4k-connect-storage-<type>. To add the module in the right place in settings.gradle.kts use the function provided.
  • There is a contract StorageContract to prove that the implementation.
  • Testcontainers can be used to prove out testing for various storage backends
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/index.html b/ecosystem/connect/index.html index 102040a5e..dcbb46b8a 100644 --- a/ecosystem/connect/index.html +++ b/ecosystem/connect/index.html @@ -82,4 +82,4 @@ The content for the documentation is now hosted alongside the main site in the repo http4k/www

\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/ai/anthropic/index.html b/ecosystem/connect/reference/ai/anthropic/index.html index 707b6b03c..6fea8e6fb 100644 --- a/ecosystem/connect/reference/ai/anthropic/index.html +++ b/ecosystem/connect/reference/ai/anthropic/index.html @@ -87,4 +87,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/ai/azure/index.html b/ecosystem/connect/reference/ai/azure/index.html index a559e2a74..18b62fe6a 100644 --- a/ecosystem/connect/reference/ai/azure/index.html +++ b/ecosystem/connect/reference/ai/azure/index.html @@ -100,4 +100,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/ai/langchain/index.html b/ecosystem/connect/reference/ai/langchain/index.html index debda0521..fd048908a 100644 --- a/ecosystem/connect/reference/ai/langchain/index.html +++ b/ecosystem/connect/reference/ai/langchain/index.html @@ -83,4 +83,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/ai/lmstudio/index.html b/ecosystem/connect/reference/ai/lmstudio/index.html index 73f2ac0f5..ebd3417a2 100644 --- a/ecosystem/connect/reference/ai/lmstudio/index.html +++ b/ecosystem/connect/reference/ai/lmstudio/index.html @@ -103,4 +103,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/ai/ollama/index.html b/ecosystem/connect/reference/ai/ollama/index.html index 0b5a96a03..5a2fd3ff6 100644 --- a/ecosystem/connect/reference/ai/ollama/index.html +++ b/ecosystem/connect/reference/ai/ollama/index.html @@ -101,4 +101,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/ai/openai/index.html b/ecosystem/connect/reference/ai/openai/index.html index aa5a6e0f1..f10515873 100644 --- a/ecosystem/connect/reference/ai/openai/index.html +++ b/ecosystem/connect/reference/ai/openai/index.html @@ -105,4 +105,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/apprunner/index.html b/ecosystem/connect/reference/amazon/apprunner/index.html index ca098fe0b..1a5dc9bb2 100644 --- a/ecosystem/connect/reference/amazon/apprunner/index.html +++ b/ecosystem/connect/reference/amazon/apprunner/index.html @@ -105,4 +105,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/cloudfront/index.html b/ecosystem/connect/reference/amazon/cloudfront/index.html index 30db37235..59b3249ff 100644 --- a/ecosystem/connect/reference/amazon/cloudfront/index.html +++ b/ecosystem/connect/reference/amazon/cloudfront/index.html @@ -100,4 +100,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/cloudwatchlogs/index.html b/ecosystem/connect/reference/amazon/cloudwatchlogs/index.html index 2531c7417..2aebaec9f 100644 --- a/ecosystem/connect/reference/amazon/cloudwatchlogs/index.html +++ b/ecosystem/connect/reference/amazon/cloudwatchlogs/index.html @@ -100,4 +100,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/cognito/index.html b/ecosystem/connect/reference/amazon/cognito/index.html index fffc2978f..f0927c158 100644 --- a/ecosystem/connect/reference/amazon/cognito/index.html +++ b/ecosystem/connect/reference/amazon/cognito/index.html @@ -87,4 +87,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/containercredentials/index.html b/ecosystem/connect/reference/amazon/containercredentials/index.html index 86fcf92af..ec6272538 100644 --- a/ecosystem/connect/reference/amazon/containercredentials/index.html +++ b/ecosystem/connect/reference/amazon/containercredentials/index.html @@ -86,4 +86,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/dynamodb/index.html b/ecosystem/connect/reference/amazon/dynamodb/index.html index e09192181..391c45c8b 100644 --- a/ecosystem/connect/reference/amazon/dynamodb/index.html +++ b/ecosystem/connect/reference/amazon/dynamodb/index.html @@ -248,4 +248,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/eventbridge/index.html b/ecosystem/connect/reference/amazon/eventbridge/index.html index 818d46978..65b3f304a 100644 --- a/ecosystem/connect/reference/amazon/eventbridge/index.html +++ b/ecosystem/connect/reference/amazon/eventbridge/index.html @@ -87,4 +87,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/evidently/index.html b/ecosystem/connect/reference/amazon/evidently/index.html index 70b136a0c..6f00a2b0f 100644 --- a/ecosystem/connect/reference/amazon/evidently/index.html +++ b/ecosystem/connect/reference/amazon/evidently/index.html @@ -127,4 +127,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/firehose/index.html b/ecosystem/connect/reference/amazon/firehose/index.html index c810aa236..3b17010cc 100644 --- a/ecosystem/connect/reference/amazon/firehose/index.html +++ b/ecosystem/connect/reference/amazon/firehose/index.html @@ -88,4 +88,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/iamidentitycenter/index.html b/ecosystem/connect/reference/amazon/iamidentitycenter/index.html index 5343d27cf..ee09e8de9 100644 --- a/ecosystem/connect/reference/amazon/iamidentitycenter/index.html +++ b/ecosystem/connect/reference/amazon/iamidentitycenter/index.html @@ -92,4 +92,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/instancemetadata/index.html b/ecosystem/connect/reference/amazon/instancemetadata/index.html index 55ab2904d..f98f8aba4 100644 --- a/ecosystem/connect/reference/amazon/instancemetadata/index.html +++ b/ecosystem/connect/reference/amazon/instancemetadata/index.html @@ -155,4 +155,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/kms/index.html b/ecosystem/connect/reference/amazon/kms/index.html index ac5db9aa2..ee072608f 100644 --- a/ecosystem/connect/reference/amazon/kms/index.html +++ b/ecosystem/connect/reference/amazon/kms/index.html @@ -118,4 +118,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/lambda/index.html b/ecosystem/connect/reference/amazon/lambda/index.html index 0e69345f0..3b32c07a8 100644 --- a/ecosystem/connect/reference/amazon/lambda/index.html +++ b/ecosystem/connect/reference/amazon/lambda/index.html @@ -112,4 +112,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/s3/index.html b/ecosystem/connect/reference/amazon/s3/index.html index 5f655ec69..f775e0bf0 100644 --- a/ecosystem/connect/reference/amazon/s3/index.html +++ b/ecosystem/connect/reference/amazon/s3/index.html @@ -155,4 +155,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/secretsmanager/index.html b/ecosystem/connect/reference/amazon/secretsmanager/index.html index 9cf38d635..53e0b3fc9 100644 --- a/ecosystem/connect/reference/amazon/secretsmanager/index.html +++ b/ecosystem/connect/reference/amazon/secretsmanager/index.html @@ -111,4 +111,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/ses/index.html b/ecosystem/connect/reference/amazon/ses/index.html index ee70729d8..0140dc8fa 100644 --- a/ecosystem/connect/reference/amazon/ses/index.html +++ b/ecosystem/connect/reference/amazon/ses/index.html @@ -85,4 +85,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/sns/index.html b/ecosystem/connect/reference/amazon/sns/index.html index 6f5b0b0c1..21cd22e37 100644 --- a/ecosystem/connect/reference/amazon/sns/index.html +++ b/ecosystem/connect/reference/amazon/sns/index.html @@ -85,4 +85,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/sqs/index.html b/ecosystem/connect/reference/amazon/sqs/index.html index 5351fb281..b099783b9 100644 --- a/ecosystem/connect/reference/amazon/sqs/index.html +++ b/ecosystem/connect/reference/amazon/sqs/index.html @@ -117,4 +117,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/sts/index.html b/ecosystem/connect/reference/amazon/sts/index.html index a77b405dd..f003f9132 100644 --- a/ecosystem/connect/reference/amazon/sts/index.html +++ b/ecosystem/connect/reference/amazon/sts/index.html @@ -103,4 +103,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/amazon/systemsmanager/index.html b/ecosystem/connect/reference/amazon/systemsmanager/index.html index 1fb7c5231..ff0ac12be 100644 --- a/ecosystem/connect/reference/amazon/systemsmanager/index.html +++ b/ecosystem/connect/reference/amazon/systemsmanager/index.html @@ -108,4 +108,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/aws/index.html b/ecosystem/connect/reference/aws/index.html index 2db9006e2..c13c394a9 100644 --- a/ecosystem/connect/reference/aws/index.html +++ b/ecosystem/connect/reference/aws/index.html @@ -78,4 +78,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/github/index.html b/ecosystem/connect/reference/github/index.html index 2d71feba8..9c8a5adb2 100644 --- a/ecosystem/connect/reference/github/index.html +++ b/ecosystem/connect/reference/github/index.html @@ -81,4 +81,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/gitlab/index.html b/ecosystem/connect/reference/gitlab/index.html index df93a9d42..ba068689a 100644 --- a/ecosystem/connect/reference/gitlab/index.html +++ b/ecosystem/connect/reference/gitlab/index.html @@ -81,4 +81,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/google/analytics-ga4/index.html b/ecosystem/connect/reference/google/analytics-ga4/index.html index 58783b725..599888131 100644 --- a/ecosystem/connect/reference/google/analytics-ga4/index.html +++ b/ecosystem/connect/reference/google/analytics-ga4/index.html @@ -85,4 +85,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/google/analytics-ua/index.html b/ecosystem/connect/reference/google/analytics-ua/index.html index a79e54997..47430a5d4 100644 --- a/ecosystem/connect/reference/google/analytics-ua/index.html +++ b/ecosystem/connect/reference/google/analytics-ua/index.html @@ -85,4 +85,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/kafka/rest/index.html b/ecosystem/connect/reference/kafka/rest/index.html index 9821a1d61..667ebdfe2 100644 --- a/ecosystem/connect/reference/kafka/rest/index.html +++ b/ecosystem/connect/reference/kafka/rest/index.html @@ -128,4 +128,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/kafka/schemaregistry/index.html b/ecosystem/connect/reference/kafka/schemaregistry/index.html index f446d1237..7151e2011 100644 --- a/ecosystem/connect/reference/kafka/schemaregistry/index.html +++ b/ecosystem/connect/reference/kafka/schemaregistry/index.html @@ -83,4 +83,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/ksp/index.html b/ecosystem/connect/reference/ksp/index.html index 8a229635e..89bde37b2 100644 --- a/ecosystem/connect/reference/ksp/index.html +++ b/ecosystem/connect/reference/ksp/index.html @@ -76,4 +76,4 @@ those extensions manually and maintain the API of the client appears to contain methods for each Action.

See the How-to in the docs for details on how to use this KSP plugin.

\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/mattermost/index.html b/ecosystem/connect/reference/mattermost/index.html index 11c2c592c..42e7099ad 100644 --- a/ecosystem/connect/reference/mattermost/index.html +++ b/ecosystem/connect/reference/mattermost/index.html @@ -110,4 +110,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/overview/index.html b/ecosystem/connect/reference/overview/index.html index d71ff8035..29c5aa6fd 100644 --- a/ecosystem/connect/reference/overview/index.html +++ b/ecosystem/connect/reference/overview/index.html @@ -75,4 +75,4 @@

Reference: Module Overview

A quick reference as to what is what with the http4k Connect modules.

Cloud Services

VendorSystemIn-Memory FakeNotes
AWSAppRunner✅
AWSCloudFront✅
AWSCloudwatch Logs✅
AWSDynamoDb✅
AWSEventBridge✅
AWSEvidently✅
AWSFirehose✅
AWSIAM Identity Center✅
AWSInstance Metadata✅
AWSKMS✅
AWSLambda✅
AWSS3✅
AWSSecrets Manager✅
AWSSES✅
AWSSNS✅
AWSSQS✅
AWSSTS✅
AWSSystems Manager✅
GitHubV3 API❌Client Shell and WebHook Signing only
GitLabAPI❌Client Shell and WebHook Signing only
GoogleAnalytics GA4✅
GoogleAnalytics UA✅
KafkaRest Proxy✅
KafkaSchema Registry✅
MattermostWebHook❌


AI Services

VendorSystemIn-Memory FakeNotes
AnthropicAIAPI✅Includes content generators
AzureAIAPI✅Includes content generators and GitHubModels compatibility
LangChain4JAdapters❌Adapters to be plugged into LangChains
LM StudioAPI✅
OllamaAPI✅Includes content generators and image generation
Open AIAPI✅Includes content generators and image generation


Storage Implementations

ImplementationNotes
In-MemoryIncluded with all Fakes
File-BasedIncluded with all Fakes
JDBC
Redis
S3
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/storage/core/index.html b/ecosystem/connect/reference/storage/core/index.html index b5cb0cc99..a5478a2f7 100644 --- a/ecosystem/connect/reference/storage/core/index.html +++ b/ecosystem/connect/reference/storage/core/index.html @@ -101,4 +101,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/storage/http/index.html b/ecosystem/connect/reference/storage/http/index.html index c287245fe..82d63d6d6 100644 --- a/ecosystem/connect/reference/storage/http/index.html +++ b/ecosystem/connect/reference/storage/http/index.html @@ -85,4 +85,4 @@

Then simply use your browser to see the OpenAPI specification at http://localhost:8000:

openapi.png \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/storage/jdbc/index.html b/ecosystem/connect/reference/storage/jdbc/index.html index 1fec13ad9..38aa745e7 100644 --- a/ecosystem/connect/reference/storage/jdbc/index.html +++ b/ecosystem/connect/reference/storage/jdbc/index.html @@ -99,4 +99,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/storage/redis/index.html b/ecosystem/connect/reference/storage/redis/index.html index cf3067669..8e275dd9d 100644 --- a/ecosystem/connect/reference/storage/redis/index.html +++ b/ecosystem/connect/reference/storage/redis/index.html @@ -93,4 +93,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/connect/reference/storage/s3/index.html b/ecosystem/connect/reference/storage/s3/index.html index bb1022174..859560619 100644 --- a/ecosystem/connect/reference/storage/s3/index.html +++ b/ecosystem/connect/reference/storage/s3/index.html @@ -96,4 +96,4 @@ \ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/http4k-connect/index.html b/ecosystem/http4k-connect/index.html index 58711b922..f93d2d0b3 100644 --- a/ecosystem/http4k-connect/index.html +++ b/ecosystem/http4k-connect/index.html @@ -75,4 +75,4 @@

Http4k Connect

logo

The core ecosystem is the foundation of the http4k project, providing the essential building blocks for creating HTTP servers and clients. This ecosystem is designed to be lightweight, efficient, and testable, making it ideal for building reliable, high-performance applications.

Read More
logo

http4k Connect is designed to facilitate seamless integration with external systems and services from the client viewpoint. It is optimised for zero-reflection, ideal for native and serverless use. It ships with in-memory fakes for testing without Docker and keeps dependencies minimal for small binary sizes.

Read More
pumb
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/http4k-core/index.html b/ecosystem/http4k-core/index.html index d79e42af7..0d8482876 100644 --- a/ecosystem/http4k-core/index.html +++ b/ecosystem/http4k-core/index.html @@ -75,4 +75,4 @@

Http4k Core

logo

The core ecosystem is the foundation of the http4k project, providing the essential building blocks for creating HTTP servers and clients. This ecosystem is designed to be lightweight, efficient, and testable, making it ideal for building reliable, high-performance applications.

Read More
logo

http4k Connect is designed to facilitate seamless integration with external systems and services from the client viewpoint. It is optimised for zero-reflection, ideal for native and serverless use. It ships with in-memory fakes for testing without Docker and keeps dependencies minimal for small binary sizes.

Read More
pumb
\ No newline at end of file +|   Disclaimer   

\ No newline at end of file diff --git a/ecosystem/http4k/changelog/index.html b/ecosystem/http4k/changelog/index.html index fb937ef49..79e465712 100644 --- a/ecosystem/http4k/changelog/index.html +++ b/ecosystem/http4k/changelog/index.html @@ -495,4 +495,4 @@ and force users to use the API methods for properly constructing the objects.
  • Regex Lens added.

    • v1.0.0

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/concepts/http/index.html b/ecosystem/http4k/concepts/http/index.html index a15a12e4f..d732b2572 100644 --- a/ecosystem/http4k/concepts/http/index.html +++ b/ecosystem/http4k/concepts/http/index.html @@ -88,4 +88,4 @@

    A selective request handler, which attempts to match an incoming call against a bound HttpHandler.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/concepts/lens/index.html b/ecosystem/http4k/concepts/lens/index.html index 6f73aef4a..e0d4400e1 100644 --- a/ecosystem/http4k/concepts/lens/index.html +++ b/ecosystem/http4k/concepts/lens/index.html @@ -143,4 +143,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/concepts/server-sent-events/index.html b/ecosystem/http4k/concepts/server-sent-events/index.html index a67ff9747..74273f14b 100644 --- a/ecosystem/http4k/concepts/server-sent-events/index.html +++ b/ecosystem/http4k/concepts/server-sent-events/index.html @@ -89,4 +89,4 @@

    Applies the route matching functionality when requests for Sse connections are received by the server.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/concepts/serverless/index.html b/ecosystem/http4k/concepts/serverless/index.html index 821341e11..8ad286e83 100644 --- a/ecosystem/http4k/concepts/serverless/index.html +++ b/ecosystem/http4k/concepts/serverless/index.html @@ -79,4 +79,4 @@

    Applies decoration to a matched FnHandler before it is invoked. FnFilters can be used to apply tangental effects to the matched FnHandler such as logging, or to modify the incoming event.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/concepts/websockets/index.html b/ecosystem/http4k/concepts/websockets/index.html index 2e2af7f10..4631b9a6e 100644 --- a/ecosystem/http4k/concepts/websockets/index.html +++ b/ecosystem/http4k/concepts/websockets/index.html @@ -97,4 +97,4 @@

    Applies the route matching functionality when requests for WebSocket connections are received by the server.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/contributing/index.html b/ecosystem/http4k/contributing/index.html index 4faa9ca1e..14b8e3279 100644 --- a/ecosystem/http4k/contributing/index.html +++ b/ecosystem/http4k/contributing/index.html @@ -76,4 +76,4 @@

    Appreciation

    We love our community! See the http4k site for details!

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/index.html b/ecosystem/http4k/index.html index f0e2878a5..24d4da184 100644 --- a/ecosystem/http4k/index.html +++ b/ecosystem/http4k/index.html @@ -91,4 +91,4 @@ showcases a variety of http4k use-cases and features.

    Module feature overview

    If you’re needed it to build an HTTP application, there’s an excellent chance that http4k has a module for it. Check out the reference guide sections for details on the over 65 different built in integrations.

    Acknowledgments

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/approvaltests/index.html b/ecosystem/http4k/reference/approvaltests/index.html index ba9b98a7f..07074e7b5 100644 --- a/ecosystem/http4k/reference/approvaltests/index.html +++ b/ecosystem/http4k/reference/approvaltests/index.html @@ -191,4 +191,4 @@ storing the approval files.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/aws/index.html b/ecosystem/http4k/reference/aws/index.html index 5350793a9..1035a02a2 100644 --- a/ecosystem/http4k/reference/aws/index.html +++ b/ecosystem/http4k/reference/aws/index.html @@ -156,4 +156,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/azure/index.html b/ecosystem/http4k/reference/azure/index.html index f099af9e7..96d3b9a37 100644 --- a/ecosystem/http4k/reference/azure/index.html +++ b/ecosystem/http4k/reference/azure/index.html @@ -101,4 +101,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/chaos/index.html b/ecosystem/http4k/reference/chaos/index.html index c3f8d9d31..58b4c3d64 100644 --- a/ecosystem/http4k/reference/chaos/index.html +++ b/ecosystem/http4k/reference/chaos/index.html @@ -239,4 +239,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/clients/index.html b/ecosystem/http4k/reference/clients/index.html index 08dbacdc1..cbaba6f0e 100644 --- a/ecosystem/http4k/reference/clients/index.html +++ b/ecosystem/http4k/reference/clients/index.html @@ -296,4 +296,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/cloud_events/index.html b/ecosystem/http4k/reference/cloud_events/index.html index bf86c7ada..843f05011 100644 --- a/ecosystem/http4k/reference/cloud_events/index.html +++ b/ecosystem/http4k/reference/cloud_events/index.html @@ -155,4 +155,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/cloud_native/index.html b/ecosystem/http4k/reference/cloud_native/index.html index 93f7da7dc..8196e63c2 100644 --- a/ecosystem/http4k/reference/cloud_native/index.html +++ b/ecosystem/http4k/reference/cloud_native/index.html @@ -215,4 +215,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/config/index.html b/ecosystem/http4k/reference/config/index.html index 31dfc35b0..db089e466 100644 --- a/ecosystem/http4k/reference/config/index.html +++ b/ecosystem/http4k/reference/config/index.html @@ -150,4 +150,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/contracts/index.html b/ecosystem/http4k/reference/contracts/index.html index efb620ab8..df1738cdf 100644 --- a/ecosystem/http4k/reference/contracts/index.html +++ b/ecosystem/http4k/reference/contracts/index.html @@ -273,4 +273,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/core/index.html b/ecosystem/http4k/reference/core/index.html index e6baf4ace..486c8985c 100644 --- a/ecosystem/http4k/reference/core/index.html +++ b/ecosystem/http4k/reference/core/index.html @@ -292,4 +292,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/dataframe/index.html b/ecosystem/http4k/reference/dataframe/index.html index 664b39946..c997af0aa 100644 --- a/ecosystem/http4k/reference/dataframe/index.html +++ b/ecosystem/http4k/reference/dataframe/index.html @@ -131,4 +131,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/digest/index.html b/ecosystem/http4k/reference/digest/index.html index 40fd83e49..36bbf39e2 100644 --- a/ecosystem/http4k/reference/digest/index.html +++ b/ecosystem/http4k/reference/digest/index.html @@ -146,4 +146,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/failsafe/index.html b/ecosystem/http4k/reference/failsafe/index.html index 94accaeb1..01b1ca683 100644 --- a/ecosystem/http4k/reference/failsafe/index.html +++ b/ecosystem/http4k/reference/failsafe/index.html @@ -169,4 +169,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/graphql/index.html b/ecosystem/http4k/reference/graphql/index.html index 4838a1ed1..2d6dcc99c 100644 --- a/ecosystem/http4k/reference/graphql/index.html +++ b/ecosystem/http4k/reference/graphql/index.html @@ -155,4 +155,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/hamkrest/index.html b/ecosystem/http4k/reference/hamkrest/index.html index a0bc35148..280ca92a5 100644 --- a/ecosystem/http4k/reference/hamkrest/index.html +++ b/ecosystem/http4k/reference/hamkrest/index.html @@ -121,4 +121,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/htmx/index.html b/ecosystem/http4k/reference/htmx/index.html index 92e442ede..06f993c98 100644 --- a/ecosystem/http4k/reference/htmx/index.html +++ b/ecosystem/http4k/reference/htmx/index.html @@ -125,4 +125,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/index.html b/ecosystem/http4k/reference/index.html index 17e70285e..675ed7ba5 100644 --- a/ecosystem/http4k/reference/index.html +++ b/ecosystem/http4k/reference/index.html @@ -75,4 +75,4 @@

    extension modules and integrations

    logo

    The core ecosystem is the foundation of the http4k project, providing the essential building blocks for creating HTTP servers and clients. This ecosystem is designed to be lightweight, efficient, and testable, making it ideal for building reliable, high-performance applications.

    Read More
    logo

    http4k Connect is designed to facilitate seamless integration with external systems and services from the client viewpoint. It is optimised for zero-reflection, ideal for native and serverless use. It ships with in-memory fakes for testing without Docker and keeps dependencies minimal for small binary sizes.

    Read More
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/json/index.html b/ecosystem/http4k/reference/json/index.html index 765b4c618..cffe1f620 100644 --- a/ecosystem/http4k/reference/json/index.html +++ b/ecosystem/http4k/reference/json/index.html @@ -300,4 +300,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/jsonrpc/index.html b/ecosystem/http4k/reference/jsonrpc/index.html index 1c90b290e..5f833bfad 100644 --- a/ecosystem/http4k/reference/jsonrpc/index.html +++ b/ecosystem/http4k/reference/jsonrpc/index.html @@ -152,4 +152,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/kotest/index.html b/ecosystem/http4k/reference/kotest/index.html index 7b75011b1..d5007c73f 100644 --- a/ecosystem/http4k/reference/kotest/index.html +++ b/ecosystem/http4k/reference/kotest/index.html @@ -128,4 +128,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/micrometer/index.html b/ecosystem/http4k/reference/micrometer/index.html index 70dbacb82..57121ede6 100644 --- a/ecosystem/http4k/reference/micrometer/index.html +++ b/ecosystem/http4k/reference/micrometer/index.html @@ -123,4 +123,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/multipart/index.html b/ecosystem/http4k/reference/multipart/index.html index 594f57d0f..20b499740 100644 --- a/ecosystem/http4k/reference/multipart/index.html +++ b/ecosystem/http4k/reference/multipart/index.html @@ -84,4 +84,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/oauth/index.html b/ecosystem/http4k/reference/oauth/index.html index b0901e4f4..ff05e321e 100644 --- a/ecosystem/http4k/reference/oauth/index.html +++ b/ecosystem/http4k/reference/oauth/index.html @@ -176,4 +176,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/opentelemetry/index.html b/ecosystem/http4k/reference/opentelemetry/index.html index 814179c75..7680693c2 100644 --- a/ecosystem/http4k/reference/opentelemetry/index.html +++ b/ecosystem/http4k/reference/opentelemetry/index.html @@ -182,4 +182,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/playwright/index.html b/ecosystem/http4k/reference/playwright/index.html index 24db7dfbe..f864db276 100644 --- a/ecosystem/http4k/reference/playwright/index.html +++ b/ecosystem/http4k/reference/playwright/index.html @@ -126,4 +126,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/resilience4j/index.html b/ecosystem/http4k/reference/resilience4j/index.html index 816389066..d1b334b1b 100644 --- a/ecosystem/http4k/reference/resilience4j/index.html +++ b/ecosystem/http4k/reference/resilience4j/index.html @@ -249,4 +249,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/serverless/index.html b/ecosystem/http4k/reference/serverless/index.html index ca0ba340b..a90facb41 100644 --- a/ecosystem/http4k/reference/serverless/index.html +++ b/ecosystem/http4k/reference/serverless/index.html @@ -435,4 +435,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/servers/index.html b/ecosystem/http4k/reference/servers/index.html index b9e913da9..dbbec8a0b 100644 --- a/ecosystem/http4k/reference/servers/index.html +++ b/ecosystem/http4k/reference/servers/index.html @@ -126,4 +126,4 @@ class as a starting point and reimplement as required. See the how-to guides for an example of this in use.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/servicevirtualisation/index.html b/ecosystem/http4k/reference/servicevirtualisation/index.html index a5fe47951..6293fb7be 100644 --- a/ecosystem/http4k/reference/servicevirtualisation/index.html +++ b/ecosystem/http4k/reference/servicevirtualisation/index.html @@ -81,4 +81,4 @@

    About

    Service Virtualisation testing technology provides a way of declaring contracts which can record HTTP conversations to a custom Markdown format and then replaying them later offline. http4k provides a fully featured implementation of the Servirtium solution to implement this concept.

    The basic idea is that you define an abstract contract Class/Interface which describes the expected behaviour for a system using a Client class (aka the Client-Under-Test). This contract is then implemented twice:

    1. In a Recording contract - using a MiTM proxy which sits between the Client-Under-Test and the real service. This proxy records the HTTP traffic to a custom Markdown format which can be stored in a VCS, and can be configured to remove the dynamic sections of the traffic such as Date headers etc.
    2. In a Replaying contract - using an MiTM server which matches incoming traffic and replays a recorded conversation for the matched requests in order from the Markdown file.

    The result of these 2 implementations is that we can exercise the Client-Under-Test code against different versions of the contract without performing any actual remote calls to prove compatibility. This is important because there may be complicated orchestration required for testing against a real system, or the end service may be unavailable or flaky.

    http4k provides a few different pieces of support for [Serviritum]:

    1. [JUnit5] extensions which provide the record/replay behaviour, providing a way to record and replay contracts without the use of a real server. This is only compatible when the Client-Under-Test utilises a http4k Client, since it leverages the Server-as-a-Function paradigm.

    2. MiTM proxy servers for record/replay behaviour, by inserting themselves as a proxy in the HTTP call chain and intercepting the HTTP traffic. This is compatible with HTTP clients using any JVM technology, not just http4k services - so can be used as a general JVM-based solution for implementing Servirtium-style tests.

    3. A Storage Provider abstraction for storing and loading recorded contracts from various locations including disk and directly from GitHub.

    Examples of use

    Climate API Demo: github.com/http4k/servirtium-demo-kotlin-climate-tck. The climate API tested uses a simple programatic wrapper for World Bank’s climate-data service. It can respond to requests with XML or JSON payloads, and the http4k-testing-servirtium module can record and payback either. This is a standard showcase for Servirtium.

    Kotlin Examples:

    Java Examples:

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/strikt/index.html b/ecosystem/http4k/reference/strikt/index.html index 0eb7bf959..2346007e8 100644 --- a/ecosystem/http4k/reference/strikt/index.html +++ b/ecosystem/http4k/reference/strikt/index.html @@ -119,4 +119,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/templating/index.html b/ecosystem/http4k/reference/templating/index.html index 843e614ef..d0aaa95c6 100644 --- a/ecosystem/http4k/reference/templating/index.html +++ b/ecosystem/http4k/reference/templating/index.html @@ -152,4 +152,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/testing/index.html b/ecosystem/http4k/reference/testing/index.html index 3e184c455..3a3b5cf1f 100644 --- a/ecosystem/http4k/reference/testing/index.html +++ b/ecosystem/http4k/reference/testing/index.html @@ -79,4 +79,4 @@ here.

    Testing modules

    We have developed the following modules to help with testing:

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/tracerbullet/index.html b/ecosystem/http4k/reference/tracerbullet/index.html index 25a461d20..8595f1cf0 100644 --- a/ecosystem/http4k/reference/tracerbullet/index.html +++ b/ecosystem/http4k/reference/tracerbullet/index.html @@ -231,4 +231,4 @@

    An extended example of this technique can be found at the this repository.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/webdriver/index.html b/ecosystem/http4k/reference/webdriver/index.html index ea4c7c6f7..fd75ffb4c 100644 --- a/ecosystem/http4k/reference/webdriver/index.html +++ b/ecosystem/http4k/reference/webdriver/index.html @@ -111,4 +111,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/webhooks/index.html b/ecosystem/http4k/reference/webhooks/index.html index 7b309bc4a..bd8c647fb 100644 --- a/ecosystem/http4k/reference/webhooks/index.html +++ b/ecosystem/http4k/reference/webhooks/index.html @@ -150,4 +150,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/xml/index.html b/ecosystem/http4k/reference/xml/index.html index 479f3ed17..958a7159a 100644 --- a/ecosystem/http4k/reference/xml/index.html +++ b/ecosystem/http4k/reference/xml/index.html @@ -146,4 +146,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/http4k/reference/yaml/index.html b/ecosystem/http4k/reference/yaml/index.html index 4b647fd90..82a523af0 100644 --- a/ecosystem/http4k/reference/yaml/index.html +++ b/ecosystem/http4k/reference/yaml/index.html @@ -82,4 +82,4 @@

    About

    These modules add the ability to use YAML as a first-class citizen when reading from and to HTTP messages.

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/ecosystem/index.html b/ecosystem/index.html index 764d35247..f1bbaec3a 100644 --- a/ecosystem/index.html +++ b/ecosystem/index.html @@ -75,4 +75,4 @@

    Ecosystem Overview

    The http4k Ecosystem exists as a number of sub-ecosystems, each with its own focus and set of modules, and each designed with a philosophy of simplicity and efficiency. These modules are lightweight, with minimal dependencies, ensuring that you only pull in what you need. This makes it ideal for those seeking fine-grained control over their dependencies while keeping the overall application size manageable. This modular nature enables developers to build applications incrementally, integrating only the required components without unnecessary bloat.

    As per our ethos, another core principle of the http4k ecosystem is its test-first approach. Each module is crafted to be fully testable without needing external infrastructure, empowering developers to create reliable, well-tested applications from the outset. This focus on testing at all levels makes http4k particularly well-suited for environments where code quality and reliability are paramount.

    logo

    The core ecosystem is the foundation of the http4k project, providing the essential building blocks for creating HTTP servers and clients. This ecosystem is designed to be lightweight, efficient, and testable, making it ideal for building reliable, high-performance applications.

    Read More
    logo

    http4k Connect is designed to facilitate seamless integration with external systems and services from the client viewpoint. It is optimised for zero-reflection, ideal for native and serverless use. It ships with in-memory fakes for testing without Docker and keeps dependencies minimal for small binary sizes.

    Read More
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/faq/index.html b/faq/index.html index 2817b9ed5..1796a3e9e 100644 --- a/faq/index.html +++ b/faq/index.html @@ -81,4 +81,4 @@ of the AWS adapter function class being used (v1 or v2)

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/arrange_filters_into_stacks/index.html b/howto/arrange_filters_into_stacks/index.html index d0107c077..38cbfe52d 100644 --- a/howto/arrange_filters_into_stacks/index.html +++ b/howto/arrange_filters_into_stacks/index.html @@ -151,4 +151,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/attach_context_to_a_request/index.html b/howto/attach_context_to_a_request/index.html index 522dc6da8..052aca4b0 100644 --- a/howto/attach_context_to_a_request/index.html +++ b/howto/attach_context_to_a_request/index.html @@ -174,4 +174,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/client_as_a_function/index.html b/howto/client_as_a_function/index.html index 487997738..2f2293680 100644 --- a/howto/client_as_a_function/index.html +++ b/howto/client_as_a_function/index.html @@ -96,4 +96,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/configure_an_oauth_server/index.html b/howto/configure_an_oauth_server/index.html index f9069e83e..5e4124e5f 100644 --- a/howto/configure_an_oauth_server/index.html +++ b/howto/configure_an_oauth_server/index.html @@ -247,4 +247,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/create_a_custom_json_marshaller/index.html b/howto/create_a_custom_json_marshaller/index.html index 23eee6070..d80fbd577 100644 --- a/howto/create_a_custom_json_marshaller/index.html +++ b/howto/create_a_custom_json_marshaller/index.html @@ -190,4 +190,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/create_a_swagger_ui/index.html b/howto/create_a_swagger_ui/index.html index 853914ddd..fc7201b61 100644 --- a/howto/create_a_swagger_ui/index.html +++ b/howto/create_a_swagger_ui/index.html @@ -201,4 +201,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/customise_a_server_backend/index.html b/howto/customise_a_server_backend/index.html index 919efae89..fee4136d0 100644 --- a/howto/customise_a_server_backend/index.html +++ b/howto/customise_a_server_backend/index.html @@ -152,4 +152,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/deploy_webjars/index.html b/howto/deploy_webjars/index.html index a87f390b5..9202f3fbd 100644 --- a/howto/deploy_webjars/index.html +++ b/howto/deploy_webjars/index.html @@ -108,4 +108,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/implement-your-own-clients/index.html b/howto/implement-your-own-clients/index.html index 85b37f536..54f53ff2c 100644 --- a/howto/implement-your-own-clients/index.html +++ b/howto/implement-your-own-clients/index.html @@ -92,4 +92,4 @@

    See also the guide on using KSP to generate extension functions for your clients!

    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/index.html b/howto/index.html index 493f8743e..2fa6b4268 100644 --- a/howto/index.html +++ b/howto/index.html @@ -75,4 +75,4 @@

    How-To Guides

    The meat of the http4k documentation is in this section, in which you’ll find ready made solutions to many common use-cases. Because if you’ve got something to achieve - it’s pretty likely that we’ve probably come across it already 😉. Check out the nav on the left for the list of recipes.

    The format for the recipes contains:

    • Required Gradle dependencies
    • A brief description of the problem
    • Fully runnable code example displaying the solution.

    Think of it like a mini StackOverflow - but better because you’ve got the entire solution available to adapt to your particular use-case - 😃.

    As a community-driven project, we would welcome new or updated recipes to make http4k easier to use. The format of the new and updated recipes should follow this Markdown template.

    Read more about the theory behind How-to guides here.

    Arrange Filters into stacks

    A strategy for composing your applications

    http4k Core
    Read More
    Authentication for HTTP services

    Recipes for how to secure and authenticate HTTP services

    http4k Core
    Read More
    Client as a function

    Recipes for using http4k to consume HTTP services

    http4k Core
    Read More
    Configure an OAuth_Server

    Recipe for using http4k to create an authorization server that provides an authorization code access flow

    http4k Core
    Read More
    Create a custom JSON marshaller

    Recipes for using JSON in http4k applications with a variety of popular JSON APIS

    http4k Core
    Read More
    Customise a Server backend

    How to use write custom servers backends

    http4k Core
    Read More
    Deploy WebJars

    Recipe for using WebJars with http4k

    http4k Core
    Read More
    Implement your own clients

    How to implement your own clients for the Connect pattern

    http4k Connect
    Read More
    Integrate with OpenAPI

    Recipes for using the http4k-contract module to provide typesafe endpoints with automatically generated OpenAPI documentation

    http4k Core
    Read More
    Leverage GraphQL

    Recipe for using GraphQL plugins

    http4k Core
    Read More
    Lookup a user principal

    Recipes for looking up and populating a user principal from a request

    http4k Core
    Read More
    Make HTTP calls in parallel

    Recipe to make HTTP calls in parallel using a ThreadPoolExecutor

    http4k Core
    Read More
    Make JSON Faster

    Recipes to make JSON faster through the use of lighter reflection or code generation

    http4k Core
    Read More
    Monitor http4k

    How to monitor http4k endpoints and applications

    http4k Core
    Read More
    Pimp your Connect API Clients with KSP!

    How to use KSP to generate extension functions for your Connect clients

    http4k Connect
    Read More
    Record and replay HTTP traffic

    Recipes for using http4k to record and replay HTTP traffic

    http4k Core
    Read More
    Redoc and Swagger UI

    Create a Redoc or Swagger UI for your REST API

    http4k Core
    Read More
    Request Contexts

    Recipes for using http4k with per-request context objects

    http4k Core
    Read More
    Routing API (Advanced)

    Recipes for using the http4k composable routing API, including serving static content

    http4k Core
    Read More
    Routing API (Simple)

    Recipes for using the http4k composable routing API

    http4k Core
    Read More
    Self Document Systems with Tests

    Recipe for creating a Distributed Tracing Tree

    http4k Core
    Read More
    Serve SSE

    Recipes for using http4k with Server-Sent Events

    http4k Core
    Read More
    Serve Websocket

    Recipes for using http4k with websockets

    http4k Core
    Read More
    Server-as-a-Function

    The simplest example of an http4k application

    http4k Core
    Read More
    Structure your logs with Events

    Recipe for using http4k Events to send structured logs to external log sinks

    http4k Core
    Read More
    Test using Service Virtualisation

    Implementing Service Virtualisation using Servirtium contracts

    http4k Core
    Read More
    Typesafe your API with lenses

    Recipes for using the inbuilt http4k Lens API to marshall HTTP messages on and off the wire in a typesafe fashion

    http4k Core
    Read More
    Use a custom OAuth provider

    Recipe for using http4k with custom OAuth provider

    http4k Core
    Read More
    Use a Server backend

    Recipes for using http4k with the various Server backends

    http4k Core
    Read More
    Use a templating engine

    Recipes for using server-side templating engines with http4k applications, including hot-reload functionality

    http4k Core
    Read More
    Use Auto Content Negotiation

    Recipes for using the Auto Content Negotiation Lens to marshall and unmarshall HTTP messages of various formats

    http4k Core
    Read More
    Use HTML Forms

    Recipes for using http4k with HTML forms

    http4k Core
    Read More
    Use Multipart Forms

    Recipes for using http4k with Multipart forms

    http4k Core
    Read More
    Write different test types

    Recipes for testing http4k applications

    http4k Core
    Read More
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/integrate_with_openapi/index.html b/howto/integrate_with_openapi/index.html index 02ee65485..0fe18d1f2 100644 --- a/howto/integrate_with_openapi/index.html +++ b/howto/integrate_with_openapi/index.html @@ -203,4 +203,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/leverage_graphql/index.html b/howto/leverage_graphql/index.html index 5acd830b5..abf696544 100644 --- a/howto/leverage_graphql/index.html +++ b/howto/leverage_graphql/index.html @@ -215,4 +215,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/lookup_a_user_principal/index.html b/howto/lookup_a_user_principal/index.html index 49eb05309..b975fccad 100644 --- a/howto/lookup_a_user_principal/index.html +++ b/howto/lookup_a_user_principal/index.html @@ -107,4 +107,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/make_json_faster/index.html b/howto/make_json_faster/index.html index a3e08fa94..fb600a940 100644 --- a/howto/make_json_faster/index.html +++ b/howto/make_json_faster/index.html @@ -250,4 +250,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/make_parallel_calls/index.html b/howto/make_parallel_calls/index.html index 83c1d6f9c..1c01d0584 100644 --- a/howto/make_parallel_calls/index.html +++ b/howto/make_parallel_calls/index.html @@ -160,4 +160,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/monitor_http4k/index.html b/howto/monitor_http4k/index.html index a19c36aa9..25da7dce8 100644 --- a/howto/monitor_http4k/index.html +++ b/howto/monitor_http4k/index.html @@ -281,4 +281,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/nestable_routes/index.html b/howto/nestable_routes/index.html index 4221b5786..7b4641bb0 100644 --- a/howto/nestable_routes/index.html +++ b/howto/nestable_routes/index.html @@ -162,4 +162,4 @@

    For the typesafe contract-style routing, refer to this recipe instead,

    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/pimp-your-clients-with-ksp/index.html b/howto/pimp-your-clients-with-ksp/index.html index 7e873d3c3..391776bfc 100644 --- a/howto/pimp-your-clients-with-ksp/index.html +++ b/howto/pimp-your-clients-with-ksp/index.html @@ -108,4 +108,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/record_and_replay_http_traffic/index.html b/howto/record_and_replay_http_traffic/index.html index d0b0c80ce..89ea2eb52 100644 --- a/howto/record_and_replay_http_traffic/index.html +++ b/howto/record_and_replay_http_traffic/index.html @@ -144,4 +144,4 @@

    Concepts

    The org.http4k.traffic package contains the interfaces which make up the core concepts for traffic capture and replay. These interfaces are:

    The API has been designed to be modular so API users can provide their own implementations (store in S3 etc..).

    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/secure_and_auth_http/index.html b/howto/secure_and_auth_http/index.html index 2fe8b263f..7c075f69b 100644 --- a/howto/secure_and_auth_http/index.html +++ b/howto/secure_and_auth_http/index.html @@ -210,4 +210,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/self_document_systems_with_tests/index.html b/howto/self_document_systems_with_tests/index.html index 11882c95a..2d39aceb6 100644 --- a/howto/self_document_systems_with_tests/index.html +++ b/howto/self_document_systems_with_tests/index.html @@ -224,4 +224,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/serve_sse/index.html b/howto/serve_sse/index.html index bc7416308..ef6d70b2f 100644 --- a/howto/serve_sse/index.html +++ b/howto/serve_sse/index.html @@ -133,4 +133,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/serve_websockets/index.html b/howto/serve_websockets/index.html index f7d6be5b0..83f3b998d 100644 --- a/howto/serve_websockets/index.html +++ b/howto/serve_websockets/index.html @@ -246,4 +246,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/server_as_a_function/index.html b/howto/server_as_a_function/index.html index 51c6e5891..ee6df3e92 100644 --- a/howto/server_as_a_function/index.html +++ b/howto/server_as_a_function/index.html @@ -101,4 +101,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/simple_routing/index.html b/howto/simple_routing/index.html index 12334dbee..b48e009e7 100644 --- a/howto/simple_routing/index.html +++ b/howto/simple_routing/index.html @@ -104,4 +104,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/structure_your_logs_with_events/index.html b/howto/structure_your_logs_with_events/index.html index 9055847c2..68a09fac4 100644 --- a/howto/structure_your_logs_with_events/index.html +++ b/howto/structure_your_logs_with_events/index.html @@ -160,4 +160,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/test_using_service_virtualisation/index.html b/howto/test_using_service_virtualisation/index.html index a2e19d4d9..c2515a4e2 100644 --- a/howto/test_using_service_virtualisation/index.html +++ b/howto/test_using_service_virtualisation/index.html @@ -406,4 +406,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/typesafe_your_api_with_lenses/index.html b/howto/typesafe_your_api_with_lenses/index.html index a4acf0b06..a4a9982b1 100644 --- a/howto/typesafe_your_api_with_lenses/index.html +++ b/howto/typesafe_your_api_with_lenses/index.html @@ -172,4 +172,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/use_a_custom_oauth_provider/index.html b/howto/use_a_custom_oauth_provider/index.html index bd22c9f1c..b0e4a3eea 100644 --- a/howto/use_a_custom_oauth_provider/index.html +++ b/howto/use_a_custom_oauth_provider/index.html @@ -196,4 +196,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/use_a_server_backend/index.html b/howto/use_a_server_backend/index.html index a9b7a97ed..342165dc9 100644 --- a/howto/use_a_server_backend/index.html +++ b/howto/use_a_server_backend/index.html @@ -107,4 +107,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/use_a_templating_engine/index.html b/howto/use_a_templating_engine/index.html index 4c0025918..1b1d7bf96 100644 --- a/howto/use_a_templating_engine/index.html +++ b/howto/use_a_templating_engine/index.html @@ -115,4 +115,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/use_auto_content_negotiation/index.html b/howto/use_auto_content_negotiation/index.html index 2bbec2705..2acd7fd19 100644 --- a/howto/use_auto_content_negotiation/index.html +++ b/howto/use_auto_content_negotiation/index.html @@ -165,4 +165,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/use_html_forms/index.html b/howto/use_html_forms/index.html index 9be8d65fa..8fe92d8b4 100644 --- a/howto/use_html_forms/index.html +++ b/howto/use_html_forms/index.html @@ -165,4 +165,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/use_multipart_forms/index.html b/howto/use_multipart_forms/index.html index 35f41d0e5..dc1d74846 100644 --- a/howto/use_multipart_forms/index.html +++ b/howto/use_multipart_forms/index.html @@ -394,4 +394,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/howto/write_different_test_types/index.html b/howto/write_different_test_types/index.html index 1dacdfa9d..6c6b46656 100644 --- a/howto/write_different_test_types/index.html +++ b/howto/write_different_test_types/index.html @@ -214,4 +214,4 @@
    All How-to guides
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/index.html b/index.html index 2635e5a1f..84ffe2a8d 100644 --- a/index.html +++ b/index.html @@ -92,4 +92,4 @@ touch.

    Springer Nature Technology
    Kotlin Foundation

    Professional Services

    support

    Support

    It’s important that you can rely on your core dependencies for the long term. That’s why we offer Long Term Support packages (LTS) for http4k releases.

    Safeguard your projects
    faq

    Solve

    We’ve designed http4k to be simple to work with, but getting professional advice about effectively using it from specialist experts can 🚀 your projects.

    Unlock peak performance
    training

    Educate

    We provide hands-on training to help you get the most out of http4k. You can get help from the creators of http4k to learn how to use it effectively.

    Level up your team
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/learn/index.html b/learn/index.html index db8035127..c76eb0f8e 100644 --- a/learn/index.html +++ b/learn/index.html @@ -75,4 +75,4 @@

    About the docs

    The http4k technical documentation has been designed following the Grand Unified Theory of Documentation. Overall, the http4k developers firmly believe that API design should be natural and friendly to the user, and hence the codebase is not heavily commented. If we have done our jobs correctly, someone with the correct knowledge of a particular domain or platform should be able to implement systems using the http4k APIs by just using an IDE.

    That said, there remains a lot to be written to ensure that the basic concepts of the toolkit are written down, and that users can leverage the significant number of features that http4k provides.

    You can read more about the theory here, but essentially there are four distinct styles of useful documentation, based on what mode the reader is operating in.

    grand unified theory of documentation

    Regardless of which section you are reading, as much of the code as possible exists in the repository and is built with the rest of http4k in our CI. This has the effect of a making the code more verbose (including import statements and similar), but at the same time we can guarantee that the code compiles and you can navigate around it to find where everything is coming from. We hope you agree that this tradeoff is worth it.

    Concepts

    http4k is a simple framework based around several function types, and hopefully the ideas behind it are not difficult to grasp. This section conveys the mindset and rationale behind http4k, and lays out each of the main function types used in the toolkit and how they relate to each other.

    We recommend that all new users familiarise themselves with at least the rationale and HTTP pages of this section.

    Read more about the theory behind Concepts here.

    Tutorials

    Getting started with a new library can be quite daunting, and sometimes everyone needs a little hand holding to get comfortable with how things fit together. This section contains step-by-step guides to get you started with each of http4k’s main conceptual areas. The first tutorial will get you out of the gate and up and running in no time.

    Read more about the theory behind Tutorials here.

    How-to guides

    The meat of the http4k documentation is in this section, in which you’ll find ready made solutions to many common use-cases. Because if you’ve got something to achieve - it’s pretty likely that we’ve probably come across it already 😉.

    The format for the recipes contains:

    • Required Gradle dependencies
    • A brief description of the problem
    • Fully runnable code example displaying the solution.

    Think of it like a mini StackOverflow - but better because you’ve got the entire solution available to adapt to your particular use-case - 😃.

    As a community-driven project, we would welcome new or updated recipes to make http4k easier to use. The format of the new and updated recipes should follow this Markdown template.

    Read more about the theory behind How-to guides here.

    Ecosystem references

    In order to “fly like a butterfly and sting like a bee”, http4k is heavily modularised. This section contains more detailed technical notes on the capabilities present each of the http4k modules. It’s more of a “what” than a “why”.

    Read more about the theory behind Reference guides here.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/lts-support/index.html b/lts-support/index.html index 467b76be0..26105ecf2 100644 --- a/lts-support/index.html +++ b/lts-support/index.html @@ -75,4 +75,4 @@

    Long-Term Support (LTS)

    Enjoy long-term stability and support with http4k’s Long-Term Support (LTS) offering, designed for organisations that rely on http4k for their critical applications. Our LTS version of http4k provides guaranteed maintenance and updates for a stable release, ensuring your projects remain secure and fully functional without needing frequent upgrades. Additionally, our priority support extends up to 24 months, meaning http4k LTS is your key to maintaining focus on feature delivery while ensuring your http4k applications are future-proof.

    Access expert guidance and priority support directly from the creators and maintainers of http4k. With dedicated channels, including email and Slack, you’ll get fast resolutions to any issues or questions, backed by our deep knowledge of the http4k ecosystem. Whether it’s compatibility updates or bug fixes, our team ensures that your http4k deployment remains fully integrated with the broader Kotlin and JVM environments.

    Additionally, http4k LTS offers transparency with full access to the codebase and rapid integration of community-driven improvements. Built under a permissive Apache2 license, you can rest assured that your applications comply with industry standards while enjoying the reliability and accountability that http4k LTS support provides. Get in touch to learn more about how http4k LTS can stabilize your development process for the long term.

    Contact us

    Access to priority support

    The http4k team are here on Slack and Email to guide you through any issues or questions.

    Up to 24 months peace of mind

    Guaranteed security and bug updates for the stable release channel, allowing you to focus on feature delivery.

    Source code access

    Full access to the LTS http4k codebase for transparency and auditing.

    Frequently Asked Questions

    • What is the http4k LTS programme?

      The LTS programme is a service provided by the http4k team to ensure that your applications remain stable and secure over the long term, enabling peace of mind for organisations that rely on http4k for their critical infrastructure.

    • How long are http4k LTS versions available for?

      As standard, the open source (OSS) version of http4k releases major versions of the ecosystem on a delayed cadence which is aligned with major release dates of the JDK. As a new major http4k OSS version is released, the previous major version enters the http4k LTS programme. See the schedule below for the current timeline.

    • How will my teams access the LTS versions?

      The LTS versions of http4k are hosted in a private Maven repository. To access the these assets, you will need to sign up for the LTS programme and will be supplied with the necessary credentials.

    • What types of updates are included with in the http4k LTS programme?

      LTS version of http4k receive security and necessary bug fixes for community identified bugs. This ensures that your applications remain secure and fully functional without needing frequent upgrades.

    • What type of support is available in http4k LTS

      After signup you will be given access to both email and Slack-based support channels. The http4k team is there to help you with any issues or questions you may have regarding the LTS version of http4k libraries.

    • Can I request specialised features for the http4k LTS version?

      For stability reasons, the LTS version of http4k is focused on security and bug fixes so new features are not considered for these versions. If you have a particular feature request, please get in touch to discuss it with the team. We will then prioritise it for inclusion in the mainline release or can work with you to provide a custom build.

    Professional Services

    Support

    It’s important that you can rely on your core dependencies for the long term. That’s why we offer Long Term Support packages (LTS) for http4k releases.

    Safeguard your projects

    Solve

    We’ve designed http4k to be simple to work with, but getting professional advice about effectively using it from specialist experts can 🚀 your projects.

    Unlock peak performance

    Educate

    We provide hands-on training to help you get the most out of http4k. You can get help from the creators of http4k to learn how to use it effectively.

    Level up your team

    Let's talk

    Contact us
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/module/index.html b/module/index.html index 760238bfd..f8f29fada 100644 --- a/module/index.html +++ b/module/index.html @@ -75,4 +75,4 @@

    Module

    1 of 0
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/documenting_apis_with_openapi/index.html b/news/documenting_apis_with_openapi/index.html index 0fbbb0a40..f8ef16e22 100644 --- a/news/documenting_apis_with_openapi/index.html +++ b/news/documenting_apis_with_openapi/index.html @@ -254,4 +254,4 @@

    Taking a final look at the OpenApi UI here shows that not just has the UI been updated with the new route, but that example entries for the expected response are now displayed, as well as JSON Schema entries for the Person and Age classes in the Schemas section at the bottom.

    Wrapping up…

    Once we have the final specification document available, users of our API can use the various OpenApi Generators to generate HTTP clients in various languages for interacting with it, or to generate fake services that provide our API in their own environments (and thus enabling more simple end-to-end testing). The “Fake HTTP services” technique also enables the creation of Consumer-Driven-Contract style tests, and opens up possibilities for all kinds of interesting Chaos/failure-mode testing (you can even use the http4k-testing-chaos module to help with this 😉).

    The full source for this tutorial can be found here, or for a sense of how this all looks in when mixed into a complete http4k project, check out the http4k-by-example repo, which contains an entire TDD’d project showcasing a multitude of http4k features and testing styles.

    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/http4k_v4/index.html b/news/http4k_v4/index.html index 3c71d7d81..e5dba2115 100644 --- a/news/http4k_v4/index.html +++ b/news/http4k_v4/index.html @@ -109,4 +109,4 @@ http4k connect

    http4k-connect is the team’s newest side project, the purpose of which is to eventually standardise patterns for building 3rd party system adapters to various backend services, and for building your own Fakes (backed by data-stores such as InMemory, S3 or Redis). So far (v2.8.0.0), http4k-connect supports at least the common-use case actions for the following systems (and the API is easily extendable for non-supplied actions):

    Mostly, the existence of the project is has been driven by 2 factors:

    It’s pretty hot off the press, but will be receiving a lot of attention over the coming weeks and months, and we’ll be documenting the mechanisms in both web and live talks.

    #### That's all folks... (for the moment)

    We’re pretty excited about this release and hope the library will continue to provide powerful tools to make all of our existing (and new!) users’ lives easier in creating kick ass and rock solid HTTP applications.

    In the meantime, if you are using http4k, please consider sponsoring the project to help offset the costs of development, documentation, and support.

    If you’re using it commercially, we offer Commercial Support and Consulting to ensure you’re getting maximum value from the toolkit and its related techniques.

    As ever, we’d love to hear how we’re doing, so please drop into the comm channels to get in touch.

    Peace out.

    // the http4k team

    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/http4k_v5/index.html b/news/http4k_v5/index.html index 42ca8968a..49bafee2a 100644 --- a/news/http4k_v5/index.html +++ b/news/http4k_v5/index.html @@ -75,4 +75,4 @@

    http4k Platform v5 - New Servers, Loom, TracerBullet, OpenAI plugin SDK and more

    June 2023 / the http4k team
    http4k lego

    We’re thrilled to announce the next major release of http4k! Since the last major release, the team has been busy enhancing existing features, adding new capabilities with help from our amazing community, things that we’ve needed on our own real world projects, and a sprinkling of new magic to keep pushing the boundaries of what’s possible with the http4k technology - all 127 modules of it.

    The first thing to tell you is that we’ve hit a significant milestone and are now getting about 1 million downloads per month from Maven Central. From these numbers and our interactions with the global http4k community, it makes us very happy that so many teams are seeing the power of the Server-as-a-Function model.

    Partnership programme

    Another thing to celebrate is that http4k now has it’s first major corporate partner - the wonderful SpringerNature Technology, where http4k powers a sizeable percentage of their global content delivery platform. The http4k team thanks all the folks at SN Technology for their ongoing collaboration and support - undoubtedly the project would not be where it is now without them!

    Springer Nature Technology

    If your organisation is using the http4k platform and would like to explore potential partnership options - including access to priority support channels, training opportunities, and input into the development plan, then please [reach out](mailto:contact@http4k.org?subject=Partnership opportunities) and we’ll be in touch to see how we can work together.

    With those things out of the way, let’s get on to what you really came for - features!

    Introducing the http4k Platform: 127 modules and counting

    Before we dive into the details of the library updates themselves, we’re announcing today that for the simplicity (to both the http4k community and the team!), we are unifying all http4k ecosystem projects (currently http4k and http4k-connect) under a single major platform version number - starting with v5.

    In addition, to keep pace with Java’s own rapidly evolving ecosystem, we’re going to be switching to aligning major releases of “the Platform” with every JDK release - currently scheduled for every 6 months. This will allow us to track major-version support as features are added and removed from Java and provide an easy way for our users to track the this compatibility. For the moment, http4k and http4k-connect will still have different release cadence and individual release numbers and which are now developed using Java 20 as a base, but in the future there are plans to consolidate the projects under a single platform version.

    In terms of Java compatibility - for the foreseeable future, we are still going to compile http4k for older Java versions (we still target Java 8 as a base). Over time though, we plan to adjust our standard of support for ancient versions and introduce a paid support program for those who still need to run http4k against legacy versions of Java and require updates such as security patches. If that’s already the case for your team or project, be sure to [get in touch with the http4k team](mailto:contact@http4k.org?subject=Support for legacy JVM version) to discuss your particular needs.

    Now - 127 is a pretty big number of modules, especially for what started out with a modest 43 line spike. But we’re definitely not done yet - http4k is a solid foundation - it’s arguably one of the simplest and most test-driven web libraries on the planet. We’ve also proven in http4k-connect that those parts can be composed into an powerful integration layer. Now the http4k team intend to continue that journey - and v5 is just the start.

    http4k Updates

    In v4, we shipped a massive 197 releases (an average of 1.5 per week!) and introduced 12 new modules in a variety of areas: deployment (serverless-lambda-runtime), wire formats (moshi-yaml, jackson-csv, kondor-json), security (digest), testing (strikt), and around simpler usages of OpenAPI (Redoc/SwaggerUI). http4k 5 introduces 5 new modules and tidies up the decks for future developments.

    http4k v5 is available right now from the Toolbox, where you can configure an download a fully compilable project with any combination of the 70 available http4k modules.

    Loom support

    We’re excited to see the re-introduction of virtual threads in Java and the performance improvements that can bring to well-established servers. Loom goes gold in Java 21 and we’re going to be ready for our users to use it straight away.

    For this new major version, we’re introducing three new server backends taking advantage of Java Loom virtual threads: the SDK built-in SunHttp, Jetty, and Helidon.

    Threads

    Servers are only half of the story though - http4k will also add support for Loom-friendy HTTP clients as they get released, and is introducing support for the Loom-native Helidon client in this release. We’ll be sure to keep up-to-date with the other major HTTP client libraries as they update to support Loom.

    TracerBullet: a brand new way of getting test feedback and documenting your systems

    We’re incredibly proud to be introducing TracerBullet, an innovative testing add-on that integrates with the http4k events system. TracerBullet enables teams to focus on how their services work, not just if they work. This powerful tool will change how you approach testing and help you gain deeper insights into your services.

    As a side-effect of introducing TracerBullet, http4k can automatically generate sequence and interaction diagrams, taking advantage of existing tools such as PlantUML, Mermaid, and d2 to create living documentation for your services after each test run!

    http4k TracerBullet

    The http4k team were excited to be invited back to KotlinConf 2023, where we presented how we used the TracerBullet along with Hexagonal Design to visually document multi-service tests. You can check out the video of the presentation here or see a full example of how it works in the demo repo.

    Remodelling of Websocket and SSE support

    Various http4k backends have supported SSE and Websockets for a while, but whilst the innovation was that you could unit-test them entirely in-memory (a world first?), the models did have some restrictions in handling request filtering. As such we have reworked the support to be more consistent with the HTTP handling. This is a breaking change, but it very important for us to be able to more fully support these protocols.

    Removal of deprecated and unsupported features

    As part of the major release cycle, we’re removing all code marked as deprecated in v4 of http4k.

    We have also removed the http4k-templates-dust module due to the removal of Nashorn from the Java distribution. We understand this may impact some users, and we recommend seeking alternative solutions in the long term, but you can continue to use the existing http4k-template-dust assets which are still binary compatible with v5 of http4k.

    Upgrading from http4k v4

    If you are upgrading, the best idea is to first upgrade to the last v4 version, deal with any existing deprecations in place, then simply upgrade again the latest v5 version and repeat.

    http4k-connect Updates

    http4k-connect was conceived as a library of providing client adapters for popular cloud services based on the innovative Connect pattern. v3 of the library added 20 different modules, and covered a number of popular AWS services, as well as integrating with Kafka via HTTP.

    The power of http4k-connect is it’s ability to leverage Kotlin to provide modular adapters based around a common core. Each client endpoint is modeled as a separate “Action”? Is the action you want not supported by the core library, or do you want less information to be parsed? Simple - just write your own endpoint adapter and plug it in!

    Today with the v5 release, we’re expanding the focus slightly - http4k-connect will now be the home of all official http4k platform integrations with third party services, to cover:

    • Featherweight, zero-reflection adapters, for HTTP integrations with cloud services (eg. AWS, Confluent)
    • Fake implementations of cloud services, which allow lightning-fast in-memory testing or local testing without Docker/LocalStack.
    • A pluggable unified Storage interface with five different storage backends - including in-memory, Redis and S3, as well as a StorageExplorer that provides an OpenAPI UI to allow interaction with the storage via browser.
    • Plugin SDKs for building integrations with popular platforms - starting with…

    OpenAI/ChatGPT support

    It’s 2023, and the new hotness that everyone is talking about is AI - and who are we to go against the weight of the hypemachine? After playing with GPT-4, one of the most frustrating things we found was the slowness of the responses and the effect that had on our testing-cycle, so the http4k team started to build a client adapter and fake OpenAI server so that Kotlin developer teams could integrate and test with OpenAI APIs quickly without waiting ages for the model to respond, and burning through those precious GPT-4 tokens and API limits. And thus http4k-connect-openai was born. The Fake server even allows you to generate images.

    A little later, the team received an early access invite to the ChatGPT plugin programme and it immediately occured that the requirements for developing plugins were all already supported within existing http4k libraries. So we set out to develop a plugin SDK, and http4k-connect-openai-plugin was born.

    The SDK provides a simple API for developers to simply compose their plugins by supplying some config and a standard http4k-contract endpoints, which generate the required OpenAPI specifications. The SDK does the rest for you, providing the required OpenAI plugin manifest, and then protects the API with one of 4 security models - including the ability to “login with ChatGPT” and OAuth into your plugin.

    http4k openapi ChatGPT plugin

    Once created, plugins can be installed into the FakeOpenAI server, and expose a standard http4k HttpHandler which means they can be tested in memory, run locally standalone, or composed into part of a larger http4k application. It’s pretty neat and we can’t wait to see what the community uses it for!

    Removal of deprecated and unsupported features

    As part of the major release cycle, we’re removing all code marked as deprecated in v3 of http4k-connect.

    Upgrading from http4k-connect v3

    If you are upgrading, the best idea is to first upgrade to the last v3 version, deal with any existing deprecations in place, then simply upgrade again to the latest v5 version and repeat.

    And that’s it (for now!). We hope you’re as excited about these updates to the http4k platform as we are! This release brings a wealth of new features and improvements, and we believe it will make your experience using http4k technologies even better.

    Cheers

    // the http4k team

    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/index.html b/news/index.html index 7b99804aa..58798214b 100644 --- a/news/index.html +++ b/news/index.html @@ -78,4 +78,4 @@ often to keep informed about how http4k continues to evolve and how it can help you build better web applications.

    http4k Platform v5 - New Servers, Loom, TracerBullet, OpenAI plugin SDK and more
    June 2023
    There's a new major http4k release! Read about all the new things the team have been working on for http4k v5.
    Add typesafe 12-factor configuration to http4k apps with Environments
    October 2021
    An overview of how to configure http4k applications using the http4k-config module
    Reassurance to http4k users regarding JCenter shutdown
    February 2021
    Announcement regarding JCenter shutdown
    http4k v4 - 17 platforms and counting...
    January 2021
    There's a new major http4k release! Read about all the new stuff the team have been working on for http4k v4.
    http4k Toolbox - Guns for show, knives for a pro
    November 2020
    An introduction to the http4k Toolbox website and CLI.
    Nanoservices - The Power of Composition
    October 2020
    You thought that microservices were a thing? Pah! The powerful abstractions in the http4k toolkit allow you to write entire useful apps which fit in a Tweet.
    A retrospective on http4k v3
    September 2020
    In preparation for the upcoming release of v4, the http4k team thought we'd do a bit of a retrospective about all the things that have gone in the >260 releases of v3.
    Documenting http4k APIs with OpenApi3
    May 2019
    An overview of the OpenApi3 support available in the http4k library.
    Websockets. But typesafe. And testable. Without the Server.
    December 2017
    An overview of typesafe Websocket support in http4k
    Server as a Function. In Kotlin. Typesafe. Without the Server.
    November 2017
    An overview of the Kotlin "Server as a Function" library, http4k
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/meet_http4k/index.html b/news/meet_http4k/index.html index 00656a649..5653dc6d8 100644 --- a/news/meet_http4k/index.html +++ b/news/meet_http4k/index.html @@ -210,4 +210,4 @@ allow us to revisit this decision.
  • (UPDATE) Websockets? Yep - simple, testable, and now available in v3.2.1! See the introductory blog post for details!
    • All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/nanoservices/index.html b/news/nanoservices/index.html index 23d89db5a..fd5d02dde 100644 --- a/news/nanoservices/index.html +++ b/news/nanoservices/index.html @@ -384,4 +384,4 @@ [channels]: https://http4k.org/support

    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/regarding_jcenter/index.html b/news/regarding_jcenter/index.html index b8beb25f1..04c44522e 100644 --- a/news/regarding_jcenter/index.html +++ b/news/regarding_jcenter/index.html @@ -75,4 +75,4 @@

    Reassurance to http4k users regarding JCenter shutdown

    February 2021 / the http4k team

    It was announced this week that the JCenter artifact repository would be shutting down in May 2021. As JCenter was a superset of the Maven Central repository, this obviously comes as disappointing and worrying news regarding the future of Open Source software distribution for the JVM. Many builds will undoubtedly break as a result of this move.

    The http4k project currently primarily builds and distributes our 50+ artifacts to Bintray and then syncs them to Maven Central automatically. As a result of this announcement, we have totally removed any dependency on JCenter from our builds and have verified that all of our dependencies resolve correctly without it. Hence we can say with absolute confidence that:

    As of v4.3.0.0, http4k users will be unaffected by the JCenter shutdown.

    http4k has always worked on the principle of being as lightweight as possible with respect to dependencies, and this situation has rather vindicated our position. Lots of Open Source projects will not be in such a fortunate position.

    We will be investigating alternatives to JCenter to keep our build pipelines working as efficiently as possible, but the artifacts will always be available in the Maven Central and this is where we will continue to source our dependencies from.

    On a more personal note, we would remind you that now would be an excellent opportunity to show appreciation for the entirely voluntary efforts of the http4k team and sponsor the project so we can keep on supporting our users.

    // the http4k team

    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/retrospective_v3/index.html b/news/retrospective_v3/index.html index c557b8b2d..076d105fd 100644 --- a/news/retrospective_v3/index.html +++ b/news/retrospective_v3/index.html @@ -94,4 +94,4 @@
    #### Cloudy-wowdy stuff

    Just as in every codebase there is a package called “utils”, this also happens with libraries - useful code that doesn’t quite fit anywhere else, yet you just always end up needing. For http4k, these utils were about the ancillary stuff that goes around an application to make it support 12-factor ideals such as configuration and relative primitives. We didn’t want to put this stuff into the http4k-core module as we felt it wasn’t absolutely necessary (and we wanted to continue to keep the binary size of the core module down). Thus, http4k-cloudnative was born! The major feature of this module is loading typesafe Environmental configuration of applications, using - what else…

    lenses

    Yep - the reusing of the existing http4k lens system to cover configuring your apps, meaning that it’s now impossible to make easy mistakes such as setting a 10-second timeout as 10-milliseconds! You can check out exactly how to use the feature in the docs.

    #### Testing modules

    It’s no secret that the http4k team love testing - it’s part of our core DNA and the simplicity of core design would be worthless unless we could test apps built with the library simply and effectively. To that end, some of the most exciting additions that we’ve added to the library have been in the arena of testing:

    testing
    #### OpenAPI FTW

    One of the most popular and standout http4k features is the support for the OpenApi specification. Originally supporting Swagger 2 spec via the http4k-contract module, we rewrote the implementation to add support for much more complete (and consistent!) version 3 of specification in May 2019. The module will now generate fully compliant OpenAPI3 documentation, including full JSON Schema breakdowns for class models and taking advantage of Kotlin class features such as enums and nullability. Powered by the http4k lens API, this runtime system allows developers to avoid concerning themselves with tediously documenting API models which can easily go stale.

    swagger

    Serverless turnabout

    The major http4k feature in version 3.0.0 was the addition of support for Serverless backends - namely the granddaddy of Serverless - AWS Lambda. And you know what they say about the first implementation of something? They say that it’s probably wrong. Well, turns out they were right (again). When we got to introducing the second and third implementations of Serverless (Google Cloud Functions and OpenWhisk), we realised that the approach taken for AWS wasn’t very dev friendly… it relied on reflection to solve the problem of loading the Lambda function class. This actually broke one of our own cardinal rules that we set for the http4k project:

    “Absolutely no magic involved: No reflection. No annotations.” - 5th Commandment of http4k

    So - we did what any good dev team would do and replaced the magic function loading mechanism with a more developer friendly API working by class extension. Fear not readers - the guilty parties have been appropriately punished, and it (probably) won’t happen again. 😉

    serverless

    One other piece of interesting research which came out and somewhat vindicated the dependency-lite approach of http4k was Cold Start War, which performed a lot of experiments and concluded that:

    “As expected, the dependencies slow the loading down. You should keep your Functions lean, otherwise, you will pay in seconds for every cold start.” - Mikhail Shilkov

    For production deployments, we continue to recommend the use of a tool such as Proguard or R8 to massively reduce the size of packaged Serverless Function JAR file. The http4k serverless modules also ship with zero or minimal dependencies to avoid any transitive bloat that might occur.

    Going native

    Apart from Serverless, one of the most exciting things happening in JVM-land right now is the advent of native technologies such as Quarkus and GraalVM, giving the possibility of compiling apps direct to binaries - which give a massive performance boost. It’s a young technology and often involves various amounts of trickery to get around limitations of the native system regarding areas such as reflection. Luckily for us (and you!), http4k operates on an anti-magic principle (see the 5th commandment above) and it was a nice surprise when it occurred that, with the correct server engine (Apache for the curious), http4k applications can be packaged out-of-the-box to this format with absolutely no modifications of aforementioned trickery.

    smug-mode

    We look forward to further supporting these technologies as they develop, and will endeavour to provide custom modules to suppport teams who want to take advantage of them.

    Future echoes…

    “And the open road rolled out in front of us.” - Alexandra Bracken, In The Afterlight

    So what’s next? Well, we’ve got a load of good stuff coming up for post version 4 of http4k, the rest of 2020 and beyond. As well as the website improvements, we’ve got a bunch of tools in the works to make the library more quick-start friendly, including the ability to autogenerate advanced http4k Clients and Server stubs from OpenApi specifications - both from the command-line and from the browser. We’re also looking at improvements in the versioning scheme to better communicate breaking changes, and rolling out modules to enable better Serverless platform support.

    Whatever happens though, the focus of http4k will always be on providing a best-in-class Developer and Testing experience. We’d love to hear how we’re doing, so please drop into the comm channels to get in touch. Here’s to the future. Stay safe out there and we’ll see you in it.

    future

    // the http4k team

    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/toolbox/index.html b/news/toolbox/index.html index 07da80ac9..796127fce 100644 --- a/news/toolbox/index.html +++ b/news/toolbox/index.html @@ -108,4 +108,4 @@ We hope you'll find the various tools that we've built into the [Toolbox] useful to either get started with http4k or to make your life even more productive. As ever, let us know how we're doing, and if there are any other tools that you think might be helpful then we'd love to hear about them!
    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/typesafe_configuration/index.html b/news/typesafe_configuration/index.html index 1e970c826..68e57cf95 100644 --- a/news/typesafe_configuration/index.html +++ b/news/typesafe_configuration/index.html @@ -278,4 +278,4 @@

    As with other supported primitives, Secret is available by default in all supported Lens Locations.

    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/news/typesafe_websockets/index.html b/news/typesafe_websockets/index.html index 50e9f597f..9a3c1c5db 100644 --- a/news/typesafe_websockets/index.html +++ b/news/typesafe_websockets/index.html @@ -195,4 +195,4 @@

    Fin

    Websocket support is now available for the Jetty server backend in http4k v3.2.0. We plan to roll out support for other server-backends in due course. Have a play a let us know what you think…

    Footnotes
    All News
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/overview/index.html b/overview/index.html index d00e0c017..a310e056d 100644 --- a/overview/index.html +++ b/overview/index.html @@ -75,4 +75,4 @@

    Overview

    http4k is a Kotlin-based HTTP toolkit which is designed to be simple, lightweight, and easy to use. It is built on functional programming principles, and is designed to be testable and easy to reason about. Since it’s release it has been used in production by a vast number of companies, and has been used to build a wide range of applications, from simple microservices to complex distributed systems, garnered millions of downloads per month and powers several globally significant websites.

    The basis of http4k is inspired by the “Your Function as a Server” paper produced at Twitter in 2013, which stated that all systems boundaries could be modelled as a simple function which takes a request and returns a response. This idea is the core of http4k, and is the basis for all of the libraries and tools that have been built around it. We have refined the generic concept presented in the paper to be specific to the HTTP protocol, and have built a set of tools and libraries that make it easy to build HTTP services in a functional way. See the concepts pages for more information.

    Over time, we have extended the functional core concept to model other types of function covering WebSockets, Server-Sent Events, provided type-safe (de)construction of HTTP messages using Lenses, created function-based API clients, and proved that many things can be modelled by purely composition. But the core idea of a server as a function remains the same - simplicity.

    So in a world where there are HTTP libraries by boatload, what makes http4k different? Mostly, it’s the way it’s designed with a ruthless focus on testability, control and best-in-class Developer Experience in mind. Every part of the now sizable http4k ecosystem has been developed in accordance with a real-world need and against it’s set of core principles.

    Rationale & Ethos

    http4k was created as the distillation of 15 years worth of experience of using various server-side libraries and we’ve stolen good ideas from everywhere we can. For instance - the routing module is inspired by UtterlyIdle, the “Server as a function” and filter model is stolen from Finagle, and the contract module OpenApi generator is ported from Fintrospect. With the growing adoption of Kotlin, we wanted something that would fully leverage the features of the language and it felt like a good time to start something from scratch.

    For our purposes, we wanted something that:

    1. Was based on simple functional concepts and embraced immutability.
    2. Embraced the “Server as a Function” model a uniform server/client API.
    3. Absolutely no magic involved: No reflection. No annotations.
    4. Lightweight with minimal dependencies (apart from the Kotlin StdLib, http4k-core has zero).
    5. Embraced Test-Driven approaches, was testable outside of an HTTP container, and testing should require no custom infrastructure.
    6. Starts/stops ultra quickly.
    7. Provides typesafe HTTP message deconstruction/construction.
    8. Automatically dealt with contract breaches to remove boilerplate.
    9. Automatic generation of OpenApi documentation (including JSON Schema models).

    http4k ticks all of these boxes.

    It allow us to construct entire suites of services which can be tested either wired together without HTTP, or spun up in containers using a single line of code. The symmetric HTTP API also allows Filter chains (often called “Middleware” or “Interceptors” in other frameworks) to be constructed into reusable units/stacks for both server and client sides (eg. logging/metrics/caching…) since they can be composed together for later use.

    As a bonus, we can also easily create simple Fake servers for any HTTP contract, which means (in combination with CDC suites) you can end-to-end test micro-services in an outside-in way (using GOOS-style acceptance tests).

    Scenarios such as “what happens if this HTTP dependency continually takes > 5 seconds to respond?” are easily modelled - answers you can’t easily get if you’re faking out your dependencies inside the HTTP boundary.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/performance/index.html b/performance/index.html index 28e2e211b..27877b0d9 100644 --- a/performance/index.html +++ b/performance/index.html @@ -82,4 +82,4 @@ Rocker templating engine used for rendering.

    Multiple DB queries: results:

    Top rank: 23/145 - Jetty Loom backend

    Database driver used is Postgres Vertx Client backed by a Hikari pool.

    Single DB query: results:

    Top rank: 25/151 - Apache backend

    Database driver used is PostgreSql backed by a Hikari pool.

    Random DB updates: results:

    Top rank: 41/138 - Jetty Loom backend

    Database driver used is Postgres Vertx Client backed by a Hikari pool.

    JSON Serialization: results:

    Top rank: 59/152 - Netty backend

    The standard Argo JSON module used for JSON creation and marshalling.

    Plaintext pipelining: results:

    Top rank: 84/153 - Netty backend

    Recommendations

    Benchmark your own app’s performance trying different engines if performance is critical. The Tech Empower benchmarks attempt to simulate simple real-world scenarios, but they can behave drastically different than your app. One other consideration is test time; some engines start up much faster than others.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/privacy-policy/index.html b/privacy-policy/index.html index 657a73bcb..439f49637 100644 --- a/privacy-policy/index.html +++ b/privacy-policy/index.html @@ -75,4 +75,4 @@

    Privacy policy

    Effective date: 2024-05-20

    1. Introduction

    Welcome to http4k Ltd.

    http4k Ltd (“us”, “we”, or “our”) operates http4k.org (hereinafter referred to as “Service”).

    Our Privacy Policy governs your visit to http4k.org, and explains how we collect, safeguard and disclose information that results from your use of our Service.

    We use your data to provide and improve Service. By using Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, the terms used in this Privacy Policy have the same meanings as in our Terms and Conditions.

    Our Terms and Conditions (“Terms”) govern all use of our Service and together with the Privacy Policy constitutes your agreement with us (“agreement”).

    2. Definitions

    SERVICE means the http4k.org website operated by http4k Ltd.

    PERSONAL DATA means data about a living individual who can be identified from those data (or from those and other information either in our possession or likely to come into our possession).

    USAGE DATA is data collected automatically either generated by the use of Service or from Service infrastructure itself (for example, the duration of a page visit).

    COOKIES are small files stored on your device (computer or mobile device).

    DATA CONTROLLER means a natural or legal person who (either alone or jointly or in common with other persons) determines the purposes for which and the manner in which any personal data are, or are to be, processed. For the purpose of this Privacy Policy, we are a Data Controller of your data.

    DATA PROCESSORS (OR SERVICE PROVIDERS) means any natural or legal person who processes the data on behalf of the Data Controller. We may use the services of various Service Providers in order to process your data more effectively.

    DATA SUBJECT is any living individual who is the subject of Personal Data.

    THE USER is the individual using our Service. The User corresponds to the Data Subject, who is the subject of Personal Data.

    3. Information Collection and Use

    We collect several different types of information for various purposes to provide and improve our Service to you.

    4. Types of Data Collected

    Personal Data

    While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you (“Personal Data”). Personally identifiable information may include, but is not limited to:

    0.1. Email address

    0.2. First name and last name

    0.3. Phone number

    0.4. Address, Country, State, Province, ZIP/Postal code, City

    0.5. Cookies and Usage Data

    We may use your Personal Data to contact you with newsletters, marketing or promotional materials and other information that may be of interest to you. You may opt out of receiving any, or all, of these communications from us by following the unsubscribe link.

    Usage Data

    We may also collect information that your browser sends whenever you visit our Service or when you access Service by or through any device (“Usage Data”).

    This Usage Data may include information such as your computer’s Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

    When you access Service with a device, this Usage Data may include information such as the type of device you use, your device unique ID, the IP address of your device, your device operating system, the type of Internet browser you use, unique device identifiers and other diagnostic data.

    Tracking Cookies Data

    We use cookies and similar tracking technologies to track the activity on our Service and we hold certain information.

    Cookies are files with a small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Other tracking technologies are also used such as beacons, tags and scripts to collect and track information and to improve and analyze our Service.

    You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service.

    Examples of Cookies we use:

    0.1. Session Cookies: We use Session Cookies to operate our Service.

    0.2. Preference Cookies: We use Preference Cookies to remember your preferences and various settings.

    0.3. Security Cookies: We use Security Cookies for security purposes.

    0.4. Advertising Cookies: Advertising Cookies are used to serve you with advertisements that may be relevant to you and your interests.

    Other Data

    While using our Service, we may also collect the following information: sex, age, date of birth, place of birth, passport details, citizenship, registration at place of residence and actual address, telephone number (work, mobile), details of documents on education, qualification, professional training, employment agreements, NDA agreements, information on bonuses and compensation, information on marital status, family members, social security (or other taxpayer identification) number, office location and other data.

    5. Use of Data

    http4k Ltd uses the collected data for various purposes:

    0.1. to provide and maintain our Service;

    0.2. to notify you about changes to our Service;

    0.3. to allow you to participate in interactive features of our Service when you choose to do so;

    0.4. to provide customer support;

    0.5. to gather analysis or valuable information so that we can improve our Service;

    0.6. to monitor the usage of our Service;

    0.7. to detect, prevent and address technical issues;

    0.8. to fulfil any other purpose for which you provide it;

    0.9. to carry out our obligations and enforce our rights arising from any contracts entered into between you and us, including for billing and collection;

    0.10. to provide you with notices about your account and/or subscription, including expiration and renewal notices, email-instructions, etc.;

    0.11. to provide you with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless you have opted not to receive such information;

    0.12. in any other way we may describe when you provide the information;

    0.13. for any other purpose with your consent.

    6. Retention of Data

    We will retain your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.

    We will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period, except when this data is used to strengthen the security or to improve the functionality of our Service, or we are legally obligated to retain this data for longer time periods.

    7. Transfer of Data

    Your information, including Personal Data, may be transferred to – and maintained on – computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ from those of your jurisdiction.

    If you are located outside United States and choose to provide information to us, please note that we transfer the data, including Personal Data, to United States and process it there.

    Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.

    http4k Ltd will take all the steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organisation or a country unless there are adequate controls in place including the security of your data and other personal information.

    8. Disclosure of Data

    We may disclose personal information that we collect, or you provide:

    0.1. Disclosure for Law Enforcement.

    Under certain circumstances, we may be required to disclose your Personal Data if required to do so by law or in response to valid requests by public authorities.

    0.2. Business Transaction.

    If we or our subsidiaries are involved in a merger, acquisition or asset sale, your Personal Data may be transferred.

    0.3. Other cases. We may disclose your information also:

    0.3.1. to our subsidiaries and affiliates;

    0.3.2. to contractors, service providers, and other third parties we use to support our business;

    0.3.3. to fulfill the purpose for which you provide it;

    0.3.4. for the purpose of including your company’s logo on our website;

    0.3.5. for any other purpose disclosed by us when you provide the information;

    0.3.6. with your consent in any other cases;

    0.3.7. if we believe disclosure is necessary or appropriate to protect the rights, property, or safety of the Company, our customers, or others.

    9. Security of Data

    The security of your data is important to us but remember that no method of transmission over the Internet or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

    10. Your Data Protection Rights Under General Data Protection Regulation (GDPR)

    If you are a resident of the European Union (EU) and European Economic Area (EEA), you have certain data protection rights, covered by GDPR.

    We aim to take reasonable steps to allow you to correct, amend, delete, or limit the use of your Personal Data.

    If you wish to be informed what Personal Data we hold about you and if you want it to be removed from our systems, please email us at privacy@http4k.org.

    In certain circumstances, you have the following data protection rights:

    0.1. the right to access, update or to delete the information we have on you;

    0.2. the right of rectification. You have the right to have your information rectified if that information is inaccurate or incomplete;

    0.3. the right to object. You have the right to object to our processing of your Personal Data;

    0.4. the right of restriction. You have the right to request that we restrict the processing of your personal information;

    0.5. the right to data portability. You have the right to be provided with a copy of your Personal Data in a structured, machine-readable and commonly used format;

    0.6. the right to withdraw consent. You also have the right to withdraw your consent at any time where we rely on your consent to process your personal information;

    Please note that we may ask you to verify your identity before responding to such requests. Please note, we may not able to provide Service without some necessary data.

    You have the right to complain to a Data Protection Authority about our collection and use of your Personal Data. For more information, please contact your local data protection authority in the European Economic Area (EEA).

    11. Your Data Protection Rights under the California Privacy Protection Act (CalOPPA)

    CalOPPA is the first state law in the nation to require commercial websites and online services to post a privacy policy. The law’s reach stretches well beyond California to require a person or company in the United States (and conceivable the world) that operates websites collecting personally identifiable information from California consumers to post a conspicuous privacy policy on its website stating exactly the information being collected and those individuals with whom it is being shared, and to comply with this policy.

    According to CalOPPA we agree to the following:

    0.1. users can visit our site anonymously;

    0.2. our Privacy Policy link includes the word “Privacy”, and can easily be found on the home page of our website;

    0.3. users will be notified of any privacy policy changes on our Privacy Policy Page;

    0.4. users are able to change their personal information by emailing us at privacy@http4k.org.

    Our Policy on “Do Not Track” Signals:

    We honor Do Not Track signals and do not track, plant cookies, or use advertising when a Do Not Track browser mechanism is in place. Do Not Track is a preference you can set in your web browser to inform websites that you do not want to be tracked.

    You can enable or disable Do Not Track by visiting the Preferences or Settings page of your web browser.

    12. Your Data Protection Rights under the California Consumer Privacy Act (CCPA)

    If you are a California resident, you are entitled to learn what data we collect about you, ask to delete your data and not to sell (share) it. To exercise your data protection rights, you can make certain requests and ask us:

    0.1. What personal information we have about you. If you make this request, we will return to you:

    0.0.1. The categories of personal information we have collected about you.

    0.0.2. The categories of sources from which we collect your personal information.

    0.0.3. The business or commercial purpose for collecting or selling your personal information.

    0.0.4. The categories of third parties with whom we share personal information.

    0.0.5. The specific pieces of personal information we have collected about you.

    0.0.6. A list of categories of personal information that we have sold, along with the category of any other company we sold it to. If we have not sold your personal information, we will inform you of that fact.

    0.0.7. A list of categories of personal information that we have disclosed for a business purpose, along with the category of any other company we shared it with.

    Please note, you are entitled to ask us to provide you with this information up to two times in a rolling twelve-month period. When you make this request, the information provided may be limited to the personal information we collected about you in the previous 12 months.

    0.2. To delete your personal information. If you make this request, we will delete the personal information we hold about you as of the date of your request from our records and direct any service providers to do the same. In some cases, deletion may be accomplished through de-identification of the information. If you choose to delete your personal information, you may not be able to use certain functions that require your personal information to operate.

    0.3. To stop selling your personal information. We don’t sell or rent your personal information to any third parties for any purpose. We do not sell your personal information for monetary consideration. However, under some circumstances, a transfer of personal information to a third party, or within our family of companies, without monetary consideration may be considered a “sale” under California law. You are the only owner of your Personal Data and can request disclosure or deletion at any time.

    If you submit a request to stop selling your personal information, we will stop making such transfers.

    Please note, if you ask us to delete or stop selling your data, it may impact your experience with us, and you may not be able to participate in certain programs or membership services which require the usage of your personal information to function. But in no circumstances, we will discriminate against you for exercising your rights.

    To exercise your California data protection rights described above, please send your request(s) by email: privacy@http4k.org.

    Your data protection rights, described above, are covered by the CCPA, short for the California Consumer Privacy Act. To find out more, visit the official California Legislative Information website. The CCPA took effect on 01/01/2020.

    13. Service Providers

    We may employ third party companies and individuals to facilitate our Service (“Service Providers”), provide Service on our behalf, perform Service-related services or assist us in analysing how our Service is used.

    These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.

    14. Analytics

    We may use third-party Service Providers to monitor and analyze the use of our Service.

    15. CI/CD tools

    We may use third-party Service Providers to automate the development process of our Service.

    16. Behavioral Remarketing

    We may use remarketing services to advertise on third party websites to you after you visited our Service. We and our third-party vendors use cookies to inform, optimise and serve ads based on your past visits to our Service.

    17. Payments

    We may provide paid products and/or services within Service. In that case, we use third-party services for payment processing (e.g. payment processors).

    We will not store or collect your payment card details. That information is provided directly to our third-party payment processors whose use of your personal information is governed by their Privacy Policy. These payment processors adhere to the standards set by PCI-DSS as managed by the PCI Security Standards Council, which is a joint effort of brands like Visa, Mastercard, American Express and Discover. PCI-DSS requirements help ensure the secure handling of payment information.

    18. Links to Other Sites

    Our Service may contain links to other sites that are not operated by us. If you click a third party link, you will be directed to that third party’s site. We strongly advise you to review the Privacy Policy of every site you visit.

    We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.

    19. Children’s Privacy

    Our Services are not intended for use by children under the age of 18 (“Child” or “Children”).

    We do not knowingly collect personally identifiable information from Children under 18. If you become aware that a Child has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from Children without verification of parental consent, we take steps to remove that information from our servers.

    20. Changes to This Privacy Policy

    We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

    We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update “effective date” at the top of this Privacy Policy.

    You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

    21. Contact Us

    If you have any questions about this Privacy Policy, please contact us by email: privacy@http4k.org.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/quickstart/index.html b/quickstart/index.html index 1cd10ca0d..5d64753d3 100644 --- a/quickstart/index.html +++ b/quickstart/index.html @@ -108,4 +108,4 @@

    I want to see what http4k can do!

    We have a page dedicated to how http4k can be used in a variety of scenarios. See http4k In Action.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/rationale/index.html b/rationale/index.html index 767185662..c29041a16 100644 --- a/rationale/index.html +++ b/rationale/index.html @@ -75,4 +75,4 @@

    Rationale

    http4k was created as the distillation of 15 years worth of experience of using various server-side libraries and we’ve stolen good ideas from everywhere we can. For instance - the routing module is inspired by UtterlyIdle, the “Server as a function” and filter model is stolen from Finagle, and the contract module OpenApi generator is ported from Fintrospect. With the growing adoption of Kotlin, we wanted something that would fully leverage the features of the language and it felt like a good time to start something from scratch.

    For our purposes, we wanted something that:

    1. Was based on simple functional concepts and embraced immutability.
    2. Embraced the “Server as a Function” model a uniform server/client API.
    3. Absolutely no magic involved: No reflection. No annotations.
    4. Lightweight with minimal dependencies (apart from the Kotlin StdLib, http4k-core has zero).
    5. Embraced Test-Driven approaches, was testable outside of an HTTP container, and testing should require no custom infrastructure.
    6. Starts/stops ultra quickly.
    7. Provides typesafe HTTP message deconstruction/construction.
    8. Automatically dealt with contract breaches to remove boilerplate.
    9. Automatic generation of OpenApi documentation (including JSON Schema models).

    http4k ticks all of these boxes.

    It allow us to construct entire suites of services which can be tested either wired together without HTTP, or spun up in containers using a single line of code. The symmetric HTTP API also allows Filter chains (often called “Middleware” or “Interceptors” in other frameworks) to be constructed into reusable units/stacks for both server and client sides (eg. logging/metrics/caching…) since they can be composed together for later use.

    As a bonus, we can also easily create simple Fake servers for any HTTP contract, which means (in combination with CDC suites) you can end-to-end test micro-services in an outside-in way (using GOOS-style acceptance tests).

    Scenarios such as “what happens if this HTTP dependency continually takes > 5 seconds to respond?” are easily modelled - answers you can’t easily get if you’re faking out your dependencies inside the HTTP boundary.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/security-policy/index.html b/security-policy/index.html index 3a6ecbe78..91a1fde74 100644 --- a/security-policy/index.html +++ b/security-policy/index.html @@ -84,4 +84,4 @@ patches, and we will incorporate these changes in subsequent http4k releases.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/security/index.html b/security/index.html index a5c8144fd..1d2afea2f 100644 --- a/security/index.html +++ b/security/index.html @@ -76,4 +76,4 @@ Security Policy
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/showcase/index.html b/showcase/index.html index 1d97e19f1..d9872aa25 100644 --- a/showcase/index.html +++ b/showcase/index.html @@ -104,4 +104,4 @@ Contracts
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/solutions/index.html b/solutions/index.html index d707b9cd7..079adb4f3 100644 --- a/solutions/index.html +++ b/solutions/index.html @@ -75,4 +75,4 @@

    http4k Professional Solutions

    Maximize your productivity with http4k, leveraging the simplicity and power of the world’s most flexible and lightweight HTTP libraries. http4k Solutions equips your developers with the tools to build, modernize, and maintain cutting-edge web applications with ease.

    Scale up your http4k expertise

    On-demand training developed and curated by the maintainers of http4k, designed to upskill your team at scale.

    Modernize your apps with confidence

    Upgrade your applications to the latest version of http4k, or architect entirely new projects with our expert guidance.

    World-class support for your http4k stack

    Benefit from 24x7 support across the http4k ecosystem, ensuring stability and security for your critical systems.

    Contact us

    Consult with the creators of http4k

    Collaborate directly with the maintainers of http4k for tailored consulting and expert insights into your development needs.

    Unlock the full potential of the http4k ecosystem

    Make sure your applications leverage the latest innovations in http4k, from serverless integrations to enhanced testing capabilities.

    Empower your developers with the power of http4k

    Upskill and grow your team with the inside knowledge of http4k’s creators, helping your developers master the toolkit.

    Focus on building, not troubleshooting

    With http4k’s support and services keeping your projects up to date, your teams can stay focused on delivering great apps.

    Rely on proven development expertise

    Tap into http4k’s deep well of experience, from lightweight microservices to highly-scalable enterprise applications.

    Accelerate development, minimize distractions

    Streamline your workflow and eliminate roadblocks to maximize efficiency in delivering projects.

    Professional Services

    Support

    It’s important that you can rely on your core dependencies for the long term. That’s why we offer Long Term Support packages (LTS) for http4k releases.

    Safeguard your projects

    Solve

    We’ve designed http4k to be simple to work with, but getting professional advice about effectively using it from specialist experts can 🚀 your projects.

    Unlock peak performance

    Educate

    We provide hands-on training to help you get the most out of http4k. You can get help from the creators of http4k to learn how to use it effectively.

    Level up your team

    Let's talk

    Contact us
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/terms-and-conditions/index.html b/terms-and-conditions/index.html index df8031e13..edc02ce48 100644 --- a/terms-and-conditions/index.html +++ b/terms-and-conditions/index.html @@ -75,4 +75,4 @@

    Terms & conditions

    Last updated: 2024-05-20

    1. Introduction

    Welcome to http4k Ltd (“Company”, “we”, “our”, “us”)!

    These Terms of Service (“Terms”, “Terms of Service”) govern your use of our website located at http4k.org (together or individually “Service”) operated by http4k Ltd.

    Our Privacy Policy also governs your use of our Service and explains how we collect, safeguard and disclose information that results from your use of our web pages.

    Your agreement with us includes these Terms and our Privacy Policy (“Agreements”). You acknowledge that you have read and understood Agreements, and agree to be bound of them.

    If you do not agree with (or cannot comply with) Agreements, then you may not use the Service, but please let us know by emailing at info@http4k.org so we can try to find a solution. These Terms apply to all visitors, users and others who wish to access or use Service.

    2. Communications

    By using our Service, you agree to subscribe to newsletters, marketing or promotional materials and other information we may send. However, you may opt out of receiving any, or all, of these communications from us by following the unsubscribe link or by emailing at info@http4k.org.

    3. Purchases

    If you wish to purchase any product or service made available through Service (“Purchase”), you may be asked to supply certain information relevant to your Purchase including but not limited to, your credit or debit card number, the expiration date of your card, your billing address, and your shipping information.

    You represent and warrant that: (i) you have the legal right to use any card(s) or other payment method(s) in connection with any Purchase; and that (ii) the information you supply to us is true, correct and complete.

    We may employ the use of third party services for the purpose of facilitating payment and the completion of Purchases. By submitting your information, you grant us the right to provide the information to these third parties subject to our Privacy Policy.

    We reserve the right to refuse or cancel your order at any time for reasons including but not limited to: product or service availability, errors in the description or price of the product or service, error in your order or other reasons.

    We reserve the right to refuse or cancel your order if fraud or an unauthorized or illegal transaction is suspected.

    4. Contests, Sweepstakes and Promotions

    Any contests, sweepstakes or other promotions (collectively, “Promotions”) made available through Service may be governed by rules that are separate from these Terms of Service. If you participate in any Promotions, please review the applicable rules as well as our Privacy Policy. If the rules for a Promotion conflict with these Terms of Service, Promotion rules will apply.

    5. Subscriptions

    Some parts of Service are billed on a subscription basis (“Subscription(s)”). You will be billed in advance on a recurring and periodic basis (“Billing Cycle”). Billing cycles will be set depending on the type of subscription plan you select when purchasing a Subscription.

    At the end of each Billing Cycle, your Subscription will automatically renew under the exact same conditions unless you cancel it or http4k Ltd cancels it. You may cancel your Subscription renewal either through your online account management page or by contacting info@http4k.org customer support team.

    A valid payment method is required to process the payment for your subscription. You shall provide http4k Ltd with accurate and complete billing information that may include but not limited to full name, address, state, postal or zip code, telephone number, and a valid payment method information. By submitting such payment information, you automatically authorize http4k Ltd to charge all Subscription fees incurred through your account to any such payment instruments.

    Should automatic billing fail to occur for any reason, http4k Ltd reserves the right to terminate your access to the Service with immediate effect.

    6. Free Trial

    http4k Ltd may, at its sole discretion, offer a Subscription with a free trial for a limited period of time (“Free Trial”).

    You may be required to enter your billing information in order to sign up for Free Trial.

    If you do enter your billing information when signing up for Free Trial, you will not be charged by http4k Ltd until Free Trial has expired. On the last day of Free Trial period, unless you cancelled your Subscription, you will be automatically charged the applicable Subscription fees for the type of Subscription you have selected.

    At any time and without notice, http4k Ltd reserves the right to (i) modify Terms of Service of Free Trial offer, or (ii) cancel such Free Trial offer.

    7. Fee Changes

    http4k Ltd, in its sole discretion and at any time, may modify Subscription fees for the Subscriptions. Any Subscription fee change will become effective at the end of the then-current Billing Cycle.

    http4k Ltd will provide you with a reasonable prior notice of any change in Subscription fees to give you an opportunity to terminate your Subscription before such change becomes effective.

    Your continued use of Service after Subscription fee change comes into effect constitutes your agreement to pay the modified Subscription fee amount.

    8. Refunds

    We do not provide refunds for purchases or subscriptions you made.

    9. Content

    Content found on or through this Service are the property of http4k Ltd or used with permission. You may not distribute, modify, transmit, reuse, download, repost, copy, or use said Content, whether in whole or in part, for commercial purposes or for personal gain, without express advance written permission from us.

    10. Prohibited Uses

    You may use Service only for lawful purposes and in accordance with Terms. You agree not to use Service:

    0.1. In any way that violates any applicable national or international law or regulation.

    0.2. For the purpose of exploiting, harming, or attempting to exploit or harm minors in any way by exposing them to inappropriate content or otherwise.

    0.3. To transmit, or procure the sending of, any advertising or promotional material, including any “junk mail”, “chain letter,” “spam,” or any other similar solicitation.

    0.4. To impersonate or attempt to impersonate Company, a Company employee, another user, or any other person or entity.

    0.5. In any way that infringes upon the rights of others, or in any way is illegal, threatening, fraudulent, or harmful, or in connection with any unlawful, illegal, fraudulent, or harmful purpose or activity.

    0.6. To engage in any other conduct that restricts or inhibits anyone’s use or enjoyment of Service, or which, as determined by us, may harm or offend Company or users of Service or expose them to liability.

    Additionally, you agree not to:

    0.1. Use Service in any manner that could disable, overburden, damage, or impair Service or interfere with any other party’s use of Service, including their ability to engage in real time activities through Service.

    0.2. Use any robot, spider, or other automatic device, process, or means to access Service for any purpose, including monitoring or copying any of the material on Service.

    0.3. Use any manual process to monitor or copy any of the material on Service or for any other unauthorized purpose without our prior written consent.

    0.4. Use any device, software, or routine that interferes with the proper working of Service.

    0.5. Introduce any viruses, trojan horses, worms, logic bombs, or other material which is malicious or technologically harmful.

    0.6. Attempt to gain unauthorized access to, interfere with, damage, or disrupt any parts of Service, the server on which Service is stored, or any server, computer, or database connected to Service.

    0.7. Attack Service via a denial-of-service attack or a distributed denial-of-service attack.

    0.8. Take any action that may damage or falsify Company rating.

    0.9. Otherwise attempt to interfere with the proper working of Service.

    11. Analytics

    We may use third-party Service Providers to monitor and analyze the use of our Service.

    12. No Use By Minors

    Service is intended only for access and use by individuals at least eighteen (18) years old. By accessing or using Service, you warrant and represent that you are at least eighteen (18) years of age and with the full authority, right, and capacity to enter into this agreement and abide by all of the terms and conditions of Terms. If you are not at least eighteen (18) years old, you are prohibited from both the access and usage of Service.

    13. Accounts

    When you create an account with us, you guarantee that you are above the age of 18, and that the information you provide us is accurate, complete, and current at all times. Inaccurate, incomplete, or obsolete information may result in the immediate termination of your account on Service.

    You are responsible for maintaining the confidentiality of your account and password, including but not limited to the restriction of access to your computer and/or account. You agree to accept responsibility for any and all activities or actions that occur under your account and/or password, whether your password is with our Service or a third-party service. You must notify us immediately upon becoming aware of any breach of security or unauthorized use of your account.

    You may not use as a username the name of another person or entity or that is not lawfully available for use, a name or trademark that is subject to any rights of another person or entity other than you, without appropriate authorization. You may not use as a username any name that is offensive, vulgar or obscene.

    We reserve the right to refuse service, terminate accounts, remove or edit content, or cancel orders in our sole discretion.

    14. Intellectual Property

    Service and its original content (excluding Content provided by users), features and functionality are and will remain the exclusive property of http4k Ltd and its licensors. Service is protected by copyright, trademark, and other laws of and foreign countries. Our trademarks may not be used in connection with any product or service without the prior written consent of http4k Ltd.

    15. Copyright Policy

    We respect the intellectual property rights of others. It is our policy to respond to any claim that Content posted on Service infringes on the copyright or other intellectual property rights (“Infringement”) of any person or entity.

    If you are a copyright owner, or authorized on behalf of one, and you believe that the copyrighted work has been copied in a way that constitutes copyright infringement, please submit your claim via email to info@http4k.org, with the subject line: “Copyright Infringement” and include in your claim a detailed description of the alleged Infringement as detailed below, under “DMCA Notice and Procedure for Copyright Infringement Claims”

    You may be held accountable for damages (including costs and attorneys’ fees) for misrepresentation or bad-faith claims on the infringement of any Content found on and/or through Service on your copyright.

    16. DMCA Notice and Procedure for Copyright Infringement Claims

    You may submit a notification pursuant to the Digital Millennium Copyright Act (DMCA) by providing our Copyright Agent with the following information in writing (see 17 U.S.C 512(c)(3) for further detail):

    0.1. an electronic or physical signature of the person authorized to act on behalf of the owner of the copyright’s interest;

    0.2. a description of the copyrighted work that you claim has been infringed, including the URL (i.e., web page address) of the location where the copyrighted work exists or a copy of the copyrighted work;

    0.3. identification of the URL or other specific location on Service where the material that you claim is infringing is located;

    0.4. your address, telephone number, and email address;

    0.5. a statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law;

    0.6. a statement by you, made under penalty of perjury, that the above information in your notice is accurate and that you are the copyright owner or authorized to act on the copyright owner’s behalf.

    You can contact our Copyright Agent via email at info@http4k.org.

    17. Error Reporting and Feedback

    You may provide us either directly at info@http4k.org or via third party sites and tools with information and feedback concerning errors, suggestions for improvements, ideas, problems, complaints, and other matters related to our Service (“Feedback”). You acknowledge and agree that: (i) you shall not retain, acquire or assert any intellectual property right or other right, title or interest in or to the Feedback; (ii) Company may have development ideas similar to the Feedback; (iii) Feedback does not contain confidential information or proprietary information from you or any third party; and (iv) Company is not under any obligation of confidentiality with respect to the Feedback. In the event the transfer of the ownership to the Feedback is not possible due to applicable mandatory laws, you grant Company and its affiliates an exclusive, transferable, irrevocable, free-of-charge, sub-licensable, unlimited and perpetual right to use (including copy, modify, create derivative works, publish, distribute and commercialize) Feedback in any manner and for any purpose.

    18. Links To Other Web Sites

    Our Service may contain links to third party web sites or services that are not owned or controlled by http4k Ltd.

    http4k Ltd has no control over, and assumes no responsibility for the content, privacy policies, or practices of any third party web sites or services. We do not warrant the offerings of any of these entities/individuals or their websites.

    YOU ACKNOWLEDGE AND AGREE THAT COMPANY SHALL NOT BE RESPONSIBLE OR LIABLE, DIRECTLY OR INDIRECTLY, FOR ANY DAMAGE OR LOSS CAUSED OR ALLEGED TO BE CAUSED BY OR IN CONNECTION WITH USE OF OR RELIANCE ON ANY SUCH CONTENT, GOODS OR SERVICES AVAILABLE ON OR THROUGH ANY SUCH THIRD PARTY WEB SITES OR SERVICES.

    WE STRONGLY ADVISE YOU TO READ THE TERMS OF SERVICE AND PRIVACY POLICIES OF ANY THIRD PARTY WEB SITES OR SERVICES THAT YOU VISIT.

    19. Disclaimer Of Warranty

    THESE SERVICES ARE PROVIDED BY COMPANY ON AN “AS IS” AND “AS AVAILABLE” BASIS. COMPANY MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE OPERATION OF THEIR SERVICES, OR THE INFORMATION, CONTENT OR MATERIALS INCLUDED THEREIN. YOU EXPRESSLY AGREE THAT YOUR USE OF THESE SERVICES, THEIR CONTENT, AND ANY SERVICES OR ITEMS OBTAINED FROM US IS AT YOUR SOLE RISK.

    NEITHER COMPANY NOR ANY PERSON ASSOCIATED WITH COMPANY MAKES ANY WARRANTY OR REPRESENTATION WITH RESPECT TO THE COMPLETENESS, SECURITY, RELIABILITY, QUALITY, ACCURACY, OR AVAILABILITY OF THE SERVICES. WITHOUT LIMITING THE FOREGOING, NEITHER COMPANY NOR ANYONE ASSOCIATED WITH COMPANY REPRESENTS OR WARRANTS THAT THE SERVICES, THEIR CONTENT, OR ANY SERVICES OR ITEMS OBTAINED THROUGH THE SERVICES WILL BE ACCURATE, RELIABLE, ERROR-FREE, OR UNINTERRUPTED, THAT DEFECTS WILL BE CORRECTED, THAT THE SERVICES OR THE SERVER THAT MAKES IT AVAILABLE ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS OR THAT THE SERVICES OR ANY SERVICES OR ITEMS OBTAINED THROUGH THE SERVICES WILL OTHERWISE MEET YOUR NEEDS OR EXPECTATIONS.

    COMPANY HEREBY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR PARTICULAR PURPOSE.

    THE FOREGOING DOES NOT AFFECT ANY WARRANTIES WHICH CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW.

    20. Limitation Of Liability

    EXCEPT AS PROHIBITED BY LAW, YOU WILL HOLD US AND OUR OFFICERS, DIRECTORS, EMPLOYEES, AND AGENTS HARMLESS FOR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGE, HOWEVER IT ARISES (INCLUDING ATTORNEYS’ FEES AND ALL RELATED COSTS AND EXPENSES OF LITIGATION AND ARBITRATION, OR AT TRIAL OR ON APPEAL, IF ANY, WHETHER OR NOT LITIGATION OR ARBITRATION IS INSTITUTED), WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE, OR OTHER TORTIOUS ACTION, OR ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT, INCLUDING WITHOUT LIMITATION ANY CLAIM FOR PERSONAL INJURY OR PROPERTY DAMAGE, ARISING FROM THIS AGREEMENT AND ANY VIOLATION BY YOU OF ANY FEDERAL, STATE, OR LOCAL LAWS, STATUTES, RULES, OR REGULATIONS, EVEN IF COMPANY HAS BEEN PREVIOUSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. EXCEPT AS PROHIBITED BY LAW, IF THERE IS LIABILITY FOUND ON THE PART OF COMPANY, IT WILL BE LIMITED TO THE AMOUNT PAID FOR THE PRODUCTS AND/OR SERVICES, AND UNDER NO CIRCUMSTANCES WILL THERE BE CONSEQUENTIAL OR PUNITIVE DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF PUNITIVE, INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE PRIOR LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.

    21. Termination

    We may terminate or suspend your account and bar access to Service immediately, without prior notice or liability, under our sole discretion, for any reason whatsoever and without limitation, including but not limited to a breach of Terms.

    If you wish to terminate your account, you may simply discontinue using Service.

    All provisions of Terms which by their nature should survive termination shall survive termination, including, without limitation, ownership provisions, warranty disclaimers, indemnity and limitations of liability.

    22. Governing Law

    These Terms shall be governed and construed in accordance with the laws of England, which governing law applies to agreement without regard to its conflict of law provisions.

    Our failure to enforce any right or provision of these Terms will not be considered a waiver of those rights. If any provision of these Terms is held to be invalid or unenforceable by a court, the remaining provisions of these Terms will remain in effect. These Terms constitute the entire agreement between us regarding our Service and supersede and replace any prior agreements we might have had between us regarding Service.

    23. Changes To Service

    We reserve the right to withdraw or amend our Service, and any service or material we provide via Service, in our sole discretion without notice. We will not be liable if for any reason all or any part of Service is unavailable at any time or for any period. From time to time, we may restrict access to some parts of Service, or the entire Service, to users, including registered users.

    24. Amendments To Terms

    We may amend Terms at any time by posting the amended terms on this site. It is your responsibility to review these Terms periodically.

    Your continued use of the Platform following the posting of revised Terms means that you accept and agree to the changes. You are expected to check this page frequently so you are aware of any changes, as they are binding on you.

    By continuing to access or use our Service after any revisions become effective, you agree to be bound by the revised terms. If you do not agree to the new terms, you are no longer authorized to use Service.

    25. Waiver And Severability

    No waiver by Company of any term or condition set forth in Terms shall be deemed a further or continuing waiver of such term or condition or a waiver of any other term or condition, and any failure of Company to assert a right or provision under Terms shall not constitute a waiver of such right or provision.

    If any provision of Terms is held by a court or other tribunal of competent jurisdiction to be invalid, illegal or unenforceable for any reason, such provision shall be eliminated or limited to the minimum extent such that the remaining provisions of Terms will continue in full force and effect.

    26. Acknowledgement

    BY USING SERVICE OR OTHER SERVICES PROVIDED BY US, YOU ACKNOWLEDGE THAT YOU HAVE READ THESE TERMS OF SERVICE AND AGREE TO BE BOUND BY THEM.

    27. Contact Us

    Please send your feedback, comments, requests for technical support by email: info@http4k.org.

    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/training/index.html b/training/index.html index e6bdc1bd3..a4c9f4f56 100644 --- a/training/index.html +++ b/training/index.html @@ -75,4 +75,4 @@

    Developer Training

    The http4k project is a culmination of work on real-world projects in many different industries. Whilst the library is designed to be simple to learn and use, there are many advantages to learning from our mistakes when using it! To this end, the team have developed a significant amount of training materials which can be used to give teams new to http4k the best possible start, especially around the following areas:

    • Advanced testing strategies for individual and entire fleets of services.
    • Building, packaging and deploying http4k apps to on-premises and cloud-based environments.
    • Advanced CI/CD design.
    • Extending the http4k libraries.
    • Configuration of http4k apps for use in data-sensitive environments (customer PII protection etc).

    These materials can be delivered both remotely and in on-site sessions. If you are interested in taking advantage of our mistakes, please get in touch.

    Contact us

    Training from the experts

    No-one knows http4k better than the people who built it. Get tailored advice and support from the creators of http4k.

    Flexibility in delivery

    We can deliver training in person or remotely, depending on your needs.

    Custom courses

    Not all courses are created equal. We can tailor our training to your specific needs.

    Professional Services

    Support

    It’s important that you can rely on your core dependencies for the long term. That’s why we offer Long Term Support packages (LTS) for http4k releases.

    Safeguard your projects

    Solve

    We’ve designed http4k to be simple to work with, but getting professional advice about effectively using it from specialist experts can 🚀 your projects.

    Unlock peak performance

    Educate

    We provide hands-on training to help you get the most out of http4k. You can get help from the creators of http4k to learn how to use it effectively.

    Level up your team

    Let's talk

    Contact us
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/going_native_with_graal_on_aws_lambda/index.html b/tutorial/going_native_with_graal_on_aws_lambda/index.html index edd163ccf..48f0c4c1b 100644 --- a/tutorial/going_native_with_graal_on_aws_lambda/index.html +++ b/tutorial/going_native_with_graal_on_aws_lambda/index.html @@ -136,4 +136,4 @@

    Congratulations!

    You have successfully compiled an http4k application with GraalVM, then deployed and invoked it as a Lambda in AWS!

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/index.html b/tutorial/index.html index cd91e76f9..cd4625f6d 100644 --- a/tutorial/index.html +++ b/tutorial/index.html @@ -80,4 +80,4 @@ boilerplate. Dive in and start building your first app today!

    Your first http4k app

    A step-by-step guide creating your first running http4k app

    Read More
    Serverless http4k with AWS Lambda

    A step-by-step guide to deploying an HTTP app to AWS Lambda

    Read More
    Going native with Graal on AWS Lambda

    A step-by-step guide to compiling http4k apps with GraalVM for AWS Lambda

    Read More
    TDDing http4k Part 1: Building a walking skeleton

    A step-by-step guide to TDDing a simple http4k application

    Read More
    TDDing http4k Part 2: Adding an endpoint

    A step-by-step guide to TDDing a simple http4k application

    Read More
    TDDing http4k Part 3: Adding another endpoint

    A step-by-step guide to TDDing a simple http4k application

    Read More
    TDDing http4k Part 4: Adding an external dependency

    A step-by-step guide to TDDing a simple http4k application

    Read More
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/serverless_http4k_with_aws_lambda/index.html b/tutorial/serverless_http4k_with_aws_lambda/index.html index 603178892..4ac266822 100644 --- a/tutorial/serverless_http4k_with_aws_lambda/index.html +++ b/tutorial/serverless_http4k_with_aws_lambda/index.html @@ -182,4 +182,4 @@

    Congratulations!

    You have successfully deployed and invoked an http4k Lambda to AWS!

    To see a complete example of a similar setup, you can check out the complete AWS Lambda app from the http4k Examples repo

    (Ready for more? Let’s move on to deploying a native http4k GraalVM Lambda to AWS)

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/tdding_http4k/index.html b/tutorial/tdding_http4k/index.html index 96d68b84c..61e00f74d 100644 --- a/tutorial/tdding_http4k/index.html +++ b/tutorial/tdding_http4k/index.html @@ -75,4 +75,4 @@

    TDDing http4k

    This post is a guide to how we build http4k applications test first to provide excellent test coverage driven by decoupled tests.

    Application Design

    For this example, we will use an example of a Maths app with the following requirements:

    • The app must add 2 numbers together via an HTTP call
    • The app must multiply 2 numbers together via an HTTP call
    • Answers generated by the service will be logged (via HTTP POST) to another server - the Recorder.

    Apps can generally be split into 3 tiers:

    1. Endpoint: HttpHandlers are constructed individually, by providing a builder function which takes the business-level dependencies.
    2. Application: Builder function which takes the transport-level dependencies, and converts them into business-level dependencies. All routes are constructed and collected in this tier.
    3. Server: Builder function which takes the configuration for environmental concerns such as ports and downstream urls.

    The tutorial is split into 4 sections:

    Your first http4k app

    A step-by-step guide creating your first running http4k app

    Read More
    Serverless http4k with AWS Lambda

    A step-by-step guide to deploying an HTTP app to AWS Lambda

    Read More
    Going native with Graal on AWS Lambda

    A step-by-step guide to compiling http4k apps with GraalVM for AWS Lambda

    Read More
    TDDing http4k Part 1: Building a walking skeleton

    A step-by-step guide to TDDing a simple http4k application

    Read More
    TDDing http4k Part 2: Adding an endpoint

    A step-by-step guide to TDDing a simple http4k application

    Read More
    TDDing http4k Part 3: Adding another endpoint

    A step-by-step guide to TDDing a simple http4k application

    Read More
    TDDing http4k Part 4: Adding an external dependency

    A step-by-step guide to TDDing a simple http4k application

    Read More
    pumb
    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/tdding_http4k/part1/index.html b/tutorial/tdding_http4k/part1/index.html index 1088be8f8..8e2925d47 100644 --- a/tutorial/tdding_http4k/part1/index.html +++ b/tutorial/tdding_http4k/part1/index.html @@ -123,4 +123,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/tdding_http4k/part2/index.html b/tutorial/tdding_http4k/part2/index.html index a85c8f077..81d9a0344 100644 --- a/tutorial/tdding_http4k/part2/index.html +++ b/tutorial/tdding_http4k/part2/index.html @@ -178,4 +178,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/tdding_http4k/part3/index.html b/tutorial/tdding_http4k/part3/index.html index 0c57fd7ee..ec0edcb01 100644 --- a/tutorial/tdding_http4k/part3/index.html +++ b/tutorial/tdding_http4k/part3/index.html @@ -212,4 +212,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/tdding_http4k/part4/index.html b/tutorial/tdding_http4k/part4/index.html index d4bc3c0a8..f1f353d1a 100644 --- a/tutorial/tdding_http4k/part4/index.html +++ b/tutorial/tdding_http4k/part4/index.html @@ -304,4 +304,4 @@ \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file diff --git a/tutorial/your_first_http4k_app/index.html b/tutorial/your_first_http4k_app/index.html index 579a56fbf..af53f6b73 100644 --- a/tutorial/your_first_http4k_app/index.html +++ b/tutorial/your_first_http4k_app/index.html @@ -75,4 +75,4 @@

    Your first http4k app

    Welcome to the world of http4k! In this guide, we’ll run you through the steps required to get up and running with your first Kotlin server application. We’ll generate the project, make some requests to it and then build it into a runnable application. By the end, you’ll have a fully working app built packaged and tested using the Gradle build tool.

    Pre-requisites:

    • An internet connection
    • JDK 19 or greater installed and set up
    • An IDE/Text-editor - (http4k is developed using IntelliJ)

    Step 1

    First, we’ll generate and download a project template from the http4k Toolbox. Point your browser at toolbox.http4k.org and select the Project Wizard from the menu (alternatively, you can use the CLI to run through the same process using the command http4k generate project).

    The Toolbox is designed as a questionnaire which will help you configure a working project from all of the available http4k modules. There are several stages, but for this guide we’re just going to generate the project using the defaults.

    We explain each of the parts in the remainder of this step, but if you just want to skip to the end, just keep hitting Next until the progress bar hits 100% then go to step 2:

    toolbox

    a. First we select a deployment model for our App - Server or Serverless. Hit Next to select Server.

    b. We don’t need any realtime components such as Websockets. Hit Next.

    c. The third page allows us to select whichever Server backend we want. The default option is SunHttp which is pre-bundled with the core module. Hit Next.

    d. Next, we can choose an HTTP client. The Java HTTP Client is also pre-bundled. Hit Next.

    e. Parts 2 and 3 allows us to select bolt-on functionality and testing modules. Keep hitting Next until you get to Part 4.

    e. Now we can name the main class and package of our application. If you’re happy with the defaults (later steps will assume you are), hit Next twice.

    f. Finally, we can choose a build tool and packaging for the app. We’ll use the defaults of Gradle with ZIP distribution.

    Step 2

    Once you’re finished, the Toolbox will review your choices and you can hit Download. Unzip and import the project into your IDE. In Intellij, you choose: File -> New -> Project from existing sources. and select the build.gradle file inside the unpacked ZIP.

    Step 3

    The project is fully formed and buildable, it consists of:

    a. Build files and scripts for gradle

    b. A runnable program containing the http4k app in the src/main/kotlin directory

    c. The src/test/kotlin directory containing a working test and a runnable client program for our app.

    layout

    Step 4

    First, let’s take a tour of the /src/main/kotlin/HelloWorld.kt file which contains our production app.

    app code
    • Lines 14-18 defines our production application. It consists of a single HTTP endpoint binding all HTTP GET requests on the path /ping to an HttpHandler function. This function takes an implicit Request parameter it (which it ignores), and just constructs and returns a Response object with status and a static body string. The return type of the call to routes() is also an HttpHandler.
    • Lines 20-26 form a runnable program which starts our application.
    • Lines 21 decorates our app with a Request printing Filter. This returns another HttpHandler.
    • Lines 23 binds the app onto an instance of the SunHttp Server backend and starts it on port 9000.

    Hit the little green arrow and the application will run and start. Point your browser at http://localhost:9000/ping to check that it’s working. Note that the Filter is printing each incoming request to the console.

    Step 5

    In /src/test/kotlin/HelloWorldClient.kt there is an example of an HTTP client which we can use to call our running app.

    client code
    • Lines 12 creates an HTTP client - note that it’s type is also HttpHandler.
    • Lines 14 decorates the client with a Response printing Filter. The result type of new client is also HttpHandler.
    • Lines 16 constructs an HTTP Request and calls the client app with it, receiving a response.

    Try running the client by hitting the little green arrow on line 11. You’ll see the Response printed to the console by the Filter, followed by a repeat of the body content, which is printed by line 18.

    Step 6

    Modify the request in /src/test/kotlin/HelloWorldClient.kt to point at http://localhost:9000/pong instead. Run the client program again and note that a 404 is printed. This happens because we have not bound an HttpHandler to that endpoint.

    To bind an HttpHandler to the pong endpoint, modify /src/main/kotlin/HelloWorld.kt by adding lines 18-20 below:

    client code
    • Lines 19-21 add an HTTP endpoint binding all HTTP GET requests on the path /pong to an HttpHandler function.

    To see this update in action, first rerun the main application by hitting the green arrow now on line 23 in /src/main/kotlin/HelloWorld.kt, and then running the client again using the green arrow on line 11 in /src/test/kotlin/HelloWorldClient.kt. You should see the new “ping” response printed to the console.

    Step 7

    A test for our app is found in /src/test/kotlin/HelloWorldTest.kt. Run it with the green arrow on line 10 and it should pass.

    client code

    Cool things to notice about the test:

    1. As our app is just an HttpHandler function, it runs entirely in-memory. It is therefore super-fast and completely threadsafe.
    2. There is no custom core or other setup required for the test to run.
    3. Request and Response objects are immutable data classes, and can therefore be compared safely in tests.

    Step 8

    Let’s package our app into a runnable Application. From the IDE run the distZip task. This will create an standard application ZIP file with scripts to run the app and deposit it in the build/distributions directory. You’ll find the task in the Gradle tab under: HelloWorld -> Tasks -> Dstribution -> distZip.

    Congratulations!

    You have successfully:

    1. Created an working http4k project using the http4k Toolbox.
    2. Bound a simple HttpHandler function to particular HTTP endpoint.
    3. Seen how the http4k HttpHandler and Filter model provide a simple set of composable building blocks to construct HTTP applications.
    4. Tested the application entirely in-memory with no custom libraries or code.
    5. Packaged your http4k app into a ZIP file.

    To see a similar application, you can check out the complete Hello World app from the http4k Examples repo

    (Ready for more? Let’s move on to deploying your http4k app as a Serverless Lambda to AWS)

    \ No newline at end of file +|   Disclaimer   

    \ No newline at end of file