New issue
Advanced search Search tips

Issue 794377 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 18
Cc:
seanmccullough@chromium.org
zhangtiff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

CORS problem fetching revision info from googlesource.com

Project Member Reported by seanmccullough@chromium.org, Dec 13 2017 
Result is regression range info for alerts is missing in the UI.

From client-side console logs, while trying to load https://chromium.googlesource.com/chromium/src/+log/5dbaa985b059af42cdc5e19d5c79f98d19cd3ee5%5E..26c10f2af77308263ea018db47c048c90b88b18e?format=JSON

"No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://sheriff-o-matic.appspot.com' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."

We should either get added to their whitelist or reverse-proxy these requests.

Comment 1 by seanmccullough@chromium.org, Dec 13 2017 

Huh. On staging I get a different error, which makes it sound like CORS *is* configured correctly for prod but not for staging.

"Failed to load https://chromium.googlesource.com/chromium/src/+log/54794b55e781258bde11a417eaa69f8c69c08671%5E..e63928b653566bc6c3bfc9a5157d32fe74055db1?format=JSON: The 'Access-Control-Allow-Origin' header has a value 'https://sheriff-o-matic.appspot.com' that is not equal to the supplied origin. Origin 'https://sheriff-o-matic-staging.appspot.com' is therefore not allowed access. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 13

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by seanmccullough@chromium.org, Dec 18

Status: WontFix (was: Untriaged)
I don't see this problem on prod any more.
►

Sign in to add a comment