Set up redirects when links change

[shreevatsa]

This is low priority, but on at least a couple of occasions I have visited pages from my browser history (URL autocompletion) that have turned out be 404s:

• https://ambuda.org/dictionaries/ (it's now at https://ambuda.org/tools/dictionaries/)
• https://ambuda.org/proofing/complete-guide/ (it's now at https://ambuda.org/proofing/help/complete-guide)

It may be nice to

• set up redirects (HTTP status 301 Moved Permanently) from earlier URLs to newer ones.
• have some monitoring for pages on which users are getting 404 errors, so that we can address them.

See also: Cool URIs don't change (Tim Berners-Lee, 1998) :-)

[akprasad]

Agreed that cool URIs don't change! I've tried to be more careful about these as Ambuda has grown out of its experimental/prototype phase, but thanks for flagging the ones I've missed.

1. Where do you think the right place for these redirects is -- at the nginx layer or at the application layer? I think the nginx config makes sense.
2. Do you think we should apply this retroactively or just apply it going forward? I tend to favor the latter, but I can see arguments either way.

[shreevatsa]

Either nginx config or app config will work — I have a slight preference for it being in the app because (AFAIK) the nginx config is not part of the repo, and having it in the app will also work locally, but I guess that may change so either should be fine.

Enough to do this going forward I think.