| icons | ||
| .gitignore | ||
| default.layout.js | ||
| get-started.page.js | ||
| how.page.js | ||
| index.page.js | ||
| publish | ||
| README.md | ||
| why.page.js | ||
404 → 307
🌲 A simple gesture for an evergreen Web.
What if links never died? What if we never broke the Web? What if it didn’t involve any extra work?
It’s possible. And easy.
Just make your 404s into 307s.
In general
-
Serve your current site from a subdomain (e.g.,
2017.your.site). -
Add the 404 to 307 rule for your server (see below) to the latest version of your site to forward links that are not found on the latest version to the previous version.
-
If you change the site again in the future, rinse and repeat.
Using Site.js
With Site.js you have to do is to create a simple text file called 4042307 in the root directory of your site. In it, place the URL of the previous version of the site that you want to forward requests to that don’t exist on the current version.
e.g., in /4042307, put:
https://2017.4042307.org
Using nginx
# nginx
location / {
error_page 404 =307 https://2017.4042307.org$request_uri;
try_files $uri $uri/ =404;
}
Learn more
- Visit the 4042307 web site.
- Read: Why?
- Read: How?
Get involved and help out.
Like this? Fund us!
Small Technology Foundation is a tiny, independent not-for-profit.
We’re building the Small Web.
We exist in part thanks to patronage by people like you. If you share our vision and want to support our work, please become a patron or donate to us today and help us continue to exist.
Canonical Git Remote: https://codeberg.org/4042307/site