From 60653c17da508e53331b1e79a238f3618c186f40 Mon Sep 17 00:00:00 2001 From: Magenta <48266942+MagentaPuppy@users.noreply.github.com> Date: Sun, 27 Mar 2022 10:44:39 +1100 Subject: [PATCH] Update the caddy error docs link (#1696) * Update the caddy server link the link there is dead, update it to the proper page on the current docs * Update content/en/templates/404.md Co-authored-by: Joe Mooring --- content/en/templates/404.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/templates/404.md b/content/en/templates/404.md index 1b82e9ebf..a2d06cf81 100644 --- a/content/en/templates/404.md +++ b/content/en/templates/404.md @@ -51,7 +51,7 @@ Your 404.html file can be set to load automatically when a visitor enters a mist * Nginx. You might specify `error_page 404 /404.html;` in your `nginx.conf` file. [Details here](https://nginx.org/en/docs/http/ngx_http_core_module.html#error_page). * Amazon AWS S3. When setting a bucket up for static web serving, you can specify the error file from within the S3 GUI. * Amazon CloudFront. You can specify the page in the Error Pages section in the CloudFront Console. [Details here](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/custom-error-pages.html) -* Caddy Server. Using `errors { 404 /404.html }`. [Details here](https://caddyserver.com/docs/errors) +* Caddy Server. Use the `handle_errors` directive to specify error pages for one or more status codes. [Details here](https://caddyserver.com/docs/caddyfile/directives/handle_errors) * Netlify. Add `/* /404.html 404` to `content/_redirects`. [Details Here](https://www.netlify.com/docs/redirects/#custom-404) * Azure Static website. You can specify the `Error document path` in the Static website configuration page of the Azure portal. [More details are available in the Static website documentation](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-static-website).