IssueTracker

This is the issue tracker for developers using the Google Photos Library API:  http://developers.google.com/photos

For feature requests for the Google Photos app, please see https://support.google.com/photos/answer/6156065?hl=en

--------------------

Before filing an issue, please read and follow these instructions carefully.

First, please search through existing issues to ensure that the feature request has not already been reported. You can start the search here: https://issuetracker.google.com/savedsearches/5157556

If the feature has already been requested, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any context of how the feature would benefit you.

Also, please verify that the functionality you are requesting is not already present in the current API and tools.

If your feature has not been requested, please provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the request:
When a web application tries to fetch photo by making request to corresponding MediaItem.baseUrl, no "access-control-allow-origin" header is exposed in response. Thus the request will be blocked by browser.

What is the purpose of this new feature?
Without this feature, web application can't actually get photo data with REST API.


Please provide any additional information below.
1. The same header exists in responses to albums.coverPhotoBaseUrl
2. The same header exists in responses from (legacy) Picasa Web Albums Data API
3. Since baseUrl is dynamically generated per application, the value of "access-control-allow-origin" does not have to be *, but reasonable to be limited to registered domains of corresponding application.