Redirects to signed S3 URLs are cached until Expires is hit

Comments

2 comments

  • Rogier Mulhuijzen

    We don't do anything with no-cache unless you configure us to do so. And yes, in the absence of max-age we do listen to Expires. Although, we do expect the value of Expires to conform to the RFC, and a value of 0 does not. So in this case, we would apply a default 120 second TTL.

  • Christoph

    Sorry for the very late reply! Ah, that makes sense! And because the default TTL was 120sec I believed that the expiry is happening along with the refresh of the signed S3 URL.

    Thanks again! :slightly_smiling:

Please sign in to leave a comment.