How can I set the S3 CORS AllowedOrigin
configuration such that it dynamically echos the requesting domain in the Access-Control-Allow-Origin
header?
In the post, "CORS with CloudFront, S3, and Multiple Domains", it is suggested that setting AllowedOrigin
to <AllowedOrigin>*</AllowedOrigin>
does this. However, S3 returns Access-Control-Allow-Origin: *
instead.
Access-Control-Allow-Origin: *
does not work in my case as I am using image.crossOrigin = "use-credentials"
in a JavaScript app. With this option, S3 returns Access-Control-Allow-Credentials: true
. Cross origin access to the image then fails because using wildcard as the allowed origin in conjunction with credentials is not permitted.
Background for why this is needed:
In my setup, access to images on S3 has to go through our domain, where authentication is required to restrict access and check if an account is authorized to access the images. If it is, the server returns a 302 redirect to an S3 URL.
For the authentication to work, image.crossOrigin = "use-credentials"
has to be set so that the request hits my server with the required credentials. (Incidentally, when I tested on Firefox 30.0 and Chrome 35.0.1916.153, if crossOrigin
is set to anonymous
, credentials are still sent. But not on Safari 7.0.4. Consistent cross-browser behavior could only be obtained using use-credentials
.).
Because browsers transparently redirects to the S3 URL, credentials are also sent.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…