make redirects to latest versions of CB curriculum use 302 status code

[davidsbailey]

Background

Hannah discovered that the 404 page on curriculum builder links to https://curriculum.code.org/csp-current/, which was redirecting to /csp-19/ rather than /csp-20/ (see discussion in slack). The problem is that we are using a 301 Moved Permanently redirect, which some browsers cache indefinitely, causing some users to continue to be redirected to the old version of the curriculum after a new one is marked as current.

Description

Use a 302 Moved Temporarily redirect from the urls listed below to the latest version of the specified curriculum, so that browsers will not cache it.

This fix may be moot, since we hope to be off of curriculum builder by this time next year, which is the next time these links would change. But the fix seems straightforward, so it seems better to do it than not to.

Testing Story

Ran the script locally, then verified each of the following links to go the right place with 302 status code:

• https://curriculum.code.org/csp-current/
• https://curriculum.code.org/csd-current/
• https://curriculum.code.org/csf-current/
• https://curriculum.code.org/plcsp/
• https://curriculum.code.org/plcsd/
• https://curriculum.code.org/plcsf/

Also verified that the updated config looks correct in S3:

Reviewer Checklist:

• Tests provide adequate coverage
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[uponthesun]

It sounds like this has already been applied in production when you ran it? Is that the normal process for applying these changes?

[davidsbailey]

What I did was

1. test out the change by modifying the S3 config in 1 of the 6 routes manually. then confirmed the site behavior updated as expected.
2. test it out again by making the change in the script in 1 of the 6 routes, then running the script. then confirmed that the S3 config and site behavior updated as expected.
3. made the change in the script in the remaining routes. ran the script, confirmed S3 config + site behavior

I'm not sure if there is a better practice here