New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 900254 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Need CORS headers

Project Member Reported by leecy@google.com, Oct 30

Issue description

Currently, prevented from making CORS requests for the sheriff JSON rotations.  build.chromium.org doesn't need CORS headers for those files, but if needed, please whitelist cros-goldeneye.corp.google.com and cros-goldeneye-staging.corp.google.com.
 
Sorry for the delay here . Manged to miss this bug. 

Created CL:
https://chromium-review.googlesource.com/c/infra/infra/+/1321549

To have the CORS headers added to legacy/* requests. 

This is currently pushed to rotang-staging.googleplex.com if you want to try it ouit .. 

It adds the "access-control-allow-origin": "*" header.
Pushed to rota-ng.appspot.com too now.
Status: Verified (was: Untriaged)
Thanks!  I've verified locally that the new URLs work, and will work on the CL to switch over.

Sign in to add a comment