Redirects and rewrites
You can add redirects to your site e.g. if you have changed the structure
of your site but want to keep old links working (as you should). Just add a
_redirects file with your redirects to the root of your public folder. The
file should list one redirect per line: first the URL that should be redirected,
followed by any whitespace, followed by the URL to redirect to. The URL to
redirect to can be an absolute URL leading to another domain.
Optionally, you can specify the HTTP status code used for the redirect after the redirect specification. By default, the redirect is a temporary redirect (technically a 302 Found HTTP status code). A common redirect status code you might want to use is 301, which represents a permanent redirect.
Example _redirects file:
/my/old/post.html /posts/old/ 301
/alternative/page/ /primary/page/
/hosting/ https://www.statichost.eu
Note that actual static files are always matched first - redirects and rewrites are only considered if no static file is found.
Rewrites and proxying
It is also possible to rewrite or proxy a request to either a page on the site itself (e.g., for SPA applications) or to a URL on a completely different service (e.g., for proxying API requests). To utilize this feature, simply set the HTTP status code to 200 at the end of your rule. This indicates that the incoming request should be served from the target URL instead.
Example of a rewrite:
/* /index.html 200
In this example, all requests will be internally rewritten to the index page. This is how you’d like a client-side Single Page Application (SPA) to work.
Wildcard matching
You can use a wildcard asterisk at the end of your “from” URL. This allows you
to specify a pattern that can match multiple routes. The matched portion can be
included in the “to” part using :splat.
Example with wildcard:
/blog/* /posts/:splat 301
In this case, a request to /blog/my-post would redirect to /posts/my-post,
effectively maintaining the dynamic nature of the URL.
