Error Pages¶

SWS provides custom HTML error pages for the HTTP 404 and 50x status errors.

This feature is enabled by default and can be controlled either by the string --page404 (SERVER_ERROR_PAGE_404) or the --page50x (SERVER_ERROR_PAGE_50X) arguments.

Below is an example of how to customize those HTML pages.

static-web-server \
    --port 8787 \
    --root ./my-public-dir \
    --page404 ./my-page-404.html \
    --page50x ./my-page-50x.html

Default .html suffixes¶

If a page does not exist at the specified path, SWS will attempt to serve a page with the same path but with an .html suffix. For example, if --page404 is set to ./my-page-404 and that file does not exist, SWS will look for ./my-page-404.html and serve it if found. This allows for convenient configuration without needing to specify the .html extension if your error pages are named with that suffix.

Fallback Page for use with Client Routers¶

It is possible to provide a HTML file to be used as fallback page when GET request paths dont exist. The fallback page will be served with a 200 status code, useful when using client routers like React Router or similar. If the path is not specified or simply doesn't exist then this feature will not be activated.

It can be set with the SERVER_FALLBACK_PAGE environment variable or with the CLI argument --page-fallback.

static-web-server \
    --port 8787 \
    --root ./my-public-dir \
    --page-fallback ./my-public-dir/index.html