From 0598e20509efa4e4d65d17d504b6707f08013ed9 Mon Sep 17 00:00:00 2001 From: Mikael Niemi <603154+miknie@users.noreply.github.com> Date: Wed, 20 Sep 2023 11:46:47 +0200 Subject: [PATCH] fix(docs) guard host link (#330) --- docs/application.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/application.md b/docs/application.md index f2cb6db..8cdb574 100644 --- a/docs/application.md +++ b/docs/application.md @@ -66,7 +66,7 @@ In the above example, the `show_users` route will have an effective route patter You can think of a guard as a simple function that accepts a _request_ object reference and returns _true_ or _false_. Formally, a guard is any object that implements the [`Guard`][guardtrait] trait. Actix Web provides several guards. You can check the [functions section][guardfuncs] of the API docs. -One of the provided guards is [`Host`][guardheader]. It can be used as a filter based on request header information. +One of the provided guards is [`Host`][guardhost]. It can be used as a filter based on request header information. @@ -92,7 +92,7 @@ Each [`ServiceConfig`][serviceconfig] can have its own `data`, `routes`, and `se [stateexample]: https://github.com/actix/examples/blob/master/basics/state/src/main.rs [guardtrait]: https://docs.rs/actix-web/4/actix_web/guard/trait.Guard.html [guardfuncs]: https://docs.rs/actix-web/4/actix_web/guard/index.html#functions -[guardheader]: https://docs.rs/actix-web/4/actix_web/guard/fn.Header.html +[guardhost]: https://docs.rs/actix-web/4/actix_web/guard/fn.Host.html [data]: https://docs.rs/actix-web/4/actix_web/web/struct.Data.html [app]: https://docs.rs/actix-web/4/actix_web/struct.App.html [appconfig]: https://docs.rs/actix-web/4/actix_web/struct.App.html#method.configure