I am working with the CDN for storing various content for both an admin tool and client application.
I understand that the CDN will be cached and may take up to 24 hours to propagate. For most client scenarios this is fine and I am able to use the following code to check if a newer version of an asset is available by using the LAST-MODIFIED in the response headers.
var request = new GetContentDownloadUrlRequest { HttpMethod = "HEAD", Key = remotePath };
For the admin tool and in a few case in the client I would like to be able to check the LAST-MODIFIED directly using the ThruCDN=false property like:
var request = new GetContentDownloadUrlRequest { HttpMethod = "HEAD", Key = remotePath, ThruCDN = false };
However, setting the ThruCDN=false cause S3 to return a 403 Forbidden error with the following message:
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message>
Is there any reason why a HEAD request does not work directly against the CDN?
Thanks