Current stuck on implementing conditional redirects in Fastly based on the header in the initial response from S3. Asking for guidance at https://community.fastly.com/t/conditionally-serving-different-content-based-on-header-in-initial-backend-response/743?u=jsick.

v22 of Fastly configs now work with courtesy re-directs.

The feature is now generally working in ltd-mason.lsst.io, ltd-keeper.lsst.io and sqr-006.lsst.io. Directory redirect objects can be added to other LTD products at any time.

• Feature is documented at https://sqr-006.lsst.io/v/DM-5894/index.html#replicating-web-server-behavior-from-s3-s-rest-api
• LTD Mason automatically uploads directory redirect objects to S3 with each build
• A new LTD Mason CLI allows directory redirect objects to be retroactively added.
• LTD Keeper ensures that directory redirect objects are made for Editions

Hey J Matt Peterson [X]: could you take a quick look and sign-off on this? Everything is working, and I’ve described the redirection schema at a high level in a section of SQR-006 that I linked above. Thanks!

J Matt Peterson [X]: I changed mason to explicitly check for /v and /builds directories. Feel free to check off “Reviewed.”

Reviewed and discussed with Jonathan. Some of the implementation details are hidden away in Fastly but noted and discussed in the SQR-006 documentation.