New issue
Advanced search Search tips

Issue 889362 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 741958
Owner: ----
Closed: Sep 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

CORS is failing when developer console is not open - but works when console is up

Reported by josephng...@aetheres.com, Sep 26

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0 Safari/605.1.15

Example URL:
you would need an account on our service first since we are restricting access with cloud front signed cookies.

Steps to reproduce the problem:
See this - https://discourse.threejs.org/t/inconsistent-behavior-of-cors-policy/4208

1. Put image on aws S3
2. Create a cloud front bistro for the bucket
3. Create img element and point it to cloud front link.
4. set the crossorigin property of the img element appropriately (either "anonymous" or "with-credentials" - I have both - local testing and production environment - respectively)
4. Run 

What is the expected behavior?
The img element should load the url with no problems

What went wrong?
The img element after some time will stop loading the img.  any repeated attempts to load the image will fail. On opening the console you'll see CORS failures about not getting cors failures with the error "No 'Access-Control-Allow-Origin' header is present on the requested resource.".   

Now open the javascript console and attempt to retrieve the content (reload the page) - and viola - everything works. 

Did this work before? No 

Chrome version: 	69.0.3497.100  Channel: n/a
OS Version: OS X 10.13.6
Flash Version: 

Tested on Firefox and it works 100% of the time.
 
Components: Blink>SecurityFeature>CORS
Components: -Internals>Network
Labels: Needs-Triage-M69
Labels: -OS-Mac
Can you take a network log; https://support.google.com/chrome/a/answer/6271171?hl=en that will help to understand what happens actually.
Labels: Needs-Feedback
A number of the elements in the logs are private.  Do you have agreements in place for handling content like this? 
Project Member

Comment 7 by sheriffbot@chromium.org, Sep 27

Cc: toyoshim@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Actually - I think I have resolved it.  It was related to this thread
https://stackoverflow.com/questions/12648809/cors-policy-on-cached-image

Mergedinto: 741958
Status: Duplicate (was: Unconfirmed)
Ah, I see. We keep two relevant issues opened, fyi.
https://bugs.chromium.org/p/chromium/issues/detail?id=741958
https://bugs.chromium.org/p/chromium/issues/detail?id=741674

Probably, it's better to discuss there if we need.

Sign in to add a comment