omahaproxy is generally not part of chrome infra. dnj@ do you know whom to forward this bug (since this is cros-omahaproxy)?

Not really :/ rsesek@ maybe?

Nope, I only maintain omahaproxy proper. I believe benhenry maintains the cros version.

RE #1, this is not part of chrome infra, so putting this in chrome infrastructure doesn't seem appropriate.

+ Josafat, Leecy - any ideas who owns this? It's not ChromeOS Infra team, and Chrome Infra says the same. 

cros-omahaproxy is no longer supported, you can get same info at Now Serving page in GE -> https://cros-goldeneye.corp.google.com/chromeos/console/listOmaha

In addition, there is already a JSON file with this information 

https://pantheon.corp.google.com/m/cloudstorage/b/chromeos-build-release-console/o/omaha_status.json

Please re-open/let us know if any changes needed to it 

omaha_status.json gives just the currently serving versions, and omaha_history.json gives all previous versions.  Let us know what account needs to be whitelisted and which file you intend to use.

Then a same request as 
https://bugs.chromium.org/p/chromium/issues/detail?id=257631

I want to be able to use XHR (or fetch) to process the current versions.



What is the expected behavior?
Being able to read response data

What went wrong?
"Origin is not allowed by Access-Control-Allow-Origin"

Josafat - we should probably turn down cros-omahaproxy, then.

Junichi, can you use gs://chromeos-build-release-console/omaha_history.json instead?  We can whitelist whichever user needs access to that file.

How do I access that file via js / XMLHttpRequest ? 

Currently https://pantheon.corp.google.com/m/cloudstorage/b/chromeos-build-release-console/o/omaha_status.json disallows CORS (and actually that sounds reasonable to me) so it's not accessible.