CORS error when using uploading to GCS from localhost
up vote
0
down vote
favorite
I'm encountering a CORS error when uploading a file to a GCS signed url from localhost via PUT request, while setting Content-Type as image/png:
Access to XMLHttpRequest at 'https://storage.googleapis.com/{{BUCKET_NAME}}/folder/image.png?Expires=1542676226&GoogleAccessId=XXXX&Signature=YYYY' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I've made sure to set the bucket's CORS policy as loosely as possible for development purposes:
$ gsutil cors get gs://{{BUCKET_NAME}}
[
{
"origin": ["*"], // also tried "http://localhost:3000"
"method": ["*"],
"responseHeader": ["*"]
}
]
Unfortunately I'm not getting anything other than 403s.
cors xmlhttprequest
google-cloud-storage asked Nov 20 at 1:23
robinnnnn
6561921
add a comment |
up vote
0
down vote
favorite
I'm encountering a CORS error when uploading a file to a GCS signed url from localhost via PUT request, while setting Content-Type as image/png:
Access to XMLHttpRequest at 'https://storage.googleapis.com/{{BUCKET_NAME}}/folder/image.png?Expires=1542676226&GoogleAccessId=XXXX&Signature=YYYY' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I've made sure to set the bucket's CORS policy as loosely as possible for development purposes:
$ gsutil cors get gs://{{BUCKET_NAME}}
[
{
"origin": ["*"], // also tried "http://localhost:3000"
"method": ["*"],
"responseHeader": ["*"]
}
]
Unfortunately I'm not getting anything other than 403s.
cors xmlhttprequest
google-cloud-storage asked Nov 20 at 1:23
robinnnnn
6561921
The fact that you’re getting 403s seems like the problem you need to solve, and the cause should be unrelated to your CORS config. The only effect your CORS config should be having is to add additional headers to response — it should definitely not be making the server block any requests with a 403.
– sideshowbarker
Nov 20 at 1:28
What method are you using to create the signed URL?
– Christopher P
Nov 20 at 17:27
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm encountering a CORS error when uploading a file to a GCS signed url from localhost via PUT request, while setting Content-Type as image/png:
Access to XMLHttpRequest at 'https://storage.googleapis.com/{{BUCKET_NAME}}/folder/image.png?Expires=1542676226&GoogleAccessId=XXXX&Signature=YYYY' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I've made sure to set the bucket's CORS policy as loosely as possible for development purposes:
$ gsutil cors get gs://{{BUCKET_NAME}}
[
{
"origin": ["*"], // also tried "http://localhost:3000"
"method": ["*"],
"responseHeader": ["*"]
}
]
Unfortunately I'm not getting anything other than 403s.
cors xmlhttprequest
google-cloud-storage asked Nov 20 at 1:23
robinnnnn
6561921
I'm encountering a CORS error when uploading a file to a GCS signed url from localhost via PUT request, while setting Content-Type as image/png:
Access to XMLHttpRequest at 'https://storage.googleapis.com/{{BUCKET_NAME}}/folder/image.png?Expires=1542676226&GoogleAccessId=XXXX&Signature=YYYY' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I've made sure to set the bucket's CORS policy as loosely as possible for development purposes:
$ gsutil cors get gs://{{BUCKET_NAME}}
[
{
"origin": ["*"], // also tried "http://localhost:3000"
"method": ["*"],
"responseHeader": ["*"]
}
]
Unfortunately I'm not getting anything other than 403s.
cors xmlhttprequest
google-cloud-storage cors xmlhttprequest
google-cloud-storage asked Nov 20 at 1:23
robinnnnn
6561921
asked Nov 20 at 1:23
robinnnnn
6561921
asked Nov 20 at 1:23
robinnnnn
6561921
asked Nov 20 at 1:23
robinnnnn
6561921
asked Nov 20 at 1:23
robinnnnn
6561921
6561921
The fact that you’re getting 403s seems like the problem you need to solve, and the cause should be unrelated to your CORS config. The only effect your CORS config should be having is to add additional headers to response — it should definitely not be making the server block any requests with a 403.
– sideshowbarker
Nov 20 at 1:28
What method are you using to create the signed URL?
– Christopher P
Nov 20 at 17:27
add a comment |
The fact that you’re getting 403s seems like the problem you need to solve, and the cause should be unrelated to your CORS config. The only effect your CORS config should be having is to add additional headers to response — it should definitely not be making the server block any requests with a 403.
– sideshowbarker
Nov 20 at 1:28
What method are you using to create the signed URL?
– Christopher P
Nov 20 at 17:27
The fact that you’re getting 403s seems like the problem you need to solve, and the cause should be unrelated to your CORS config. The only effect your CORS config should be having is to add additional headers to response — it should definitely not be making the server block any requests with a 403.
– sideshowbarker
Nov 20 at 1:28
The fact that you’re getting 403s seems like the problem you need to solve, and the cause should be unrelated to your CORS config. The only effect your CORS config should be having is to add additional headers to response — it should definitely not be making the server block any requests with a 403.
– sideshowbarker
Nov 20 at 1:28
What method are you using to create the signed URL?
– Christopher P
Nov 20 at 17:27
What method are you using to create the signed URL?
– Christopher P
Nov 20 at 17:27
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53384929%2fcors-error-when-using-uploading-to-gcs-from-localhost%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The fact that you’re getting 403s seems like the problem you need to solve, and the cause should be unrelated to your CORS config. The only effect your CORS config should be having is to add additional headers to response — it should definitely not be making the server block any requests with a 403.
– sideshowbarker
Nov 20 at 1:28
What method are you using to create the signed URL?
– Christopher P
Nov 20 at 17:27