A hint: This file contains one or more very long lines, so maybe it is better readable using the pure text view mode that shows the contents as wrapped lines within the browser window.
When using Hugo with GitHub
Pages, you can provide your own template for a custom
404 error page by creating a 404.html template file in the root of
your layouts
folder. When Hugo generates your site, the
404.html
file will be placed in the root.
404 pages will have all the regular page variables available to use in the templates.
In addition to the standard page variables, the 404 page has access
to all site content accessible from .Pages
.
▾ layouts/ 404.html
This is a basic example of a 404.html template:
{{< code file="layouts/404.html" >}} {{ define "main" }}
Your 404.html file can be set to load automatically when a visitor enters a mistaken URL path, dependent upon the web serving environment you are using. For example:
ErrorDocument 404 /404.html
in
an .htaccess
file in the root of your site.error_page 404 /404.html;
in
your nginx.conf
file. Details
here.handle_errors
directive to
specify error pages for one or more status codes. Details
here/* /404.html 404
to
content/_redirects
. Details
HereresponseOverrides.404.rewrite
and responseOverrides.404.statusCode
in configfile
staticwebapp.config.json
. Details
hereError document path
in the Static website configuration
page of the Azure portal. Details
here.error_document
in your app specification file or use
control panel to set up error document. Details
here./404.html
automatically gets used as the 404
page.