Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable ampCors for analytics remote config XHR in a backward compatible way #13009

Merged
merged 3 commits into from Jan 26, 2018

Conversation

lannka
Copy link
Contributor

@lannka lannka commented Jan 24, 2018

fixes #13005

@cramforce
Copy link
Member

I'd prefer a revert (for cherry pick into prod candidate) and new PR instead of a fix unless this is super urgent.

CC @newmuis

@zhouyx zhouyx mentioned this pull request Jan 24, 2018
@zhouyx
Copy link
Contributor

zhouyx commented Jan 24, 2018

I created #13012 to revert the old PR. @newmuis let's patch that to prod.
And then also merge this real fix in normal process.

@zhouyx
Copy link
Contributor

zhouyx commented Jan 24, 2018

#13012 merged and will be patched to prod.

@lannka lannka merged commit 64f8a2c into ampproject:master Jan 26, 2018
@lannka lannka deleted the requireAmpResponseSourceOrigin branch January 26, 2018 16:08
jonkeller pushed a commit to jonkeller/amphtml that referenced this pull request Jan 29, 2018
…ble way (ampproject#13009)

* Disable ampCors for analytics remote config XHR in a backward compatible way.

* Fix test
RanAbram pushed a commit to RanAbram/amphtml that referenced this pull request Mar 12, 2018
…ble way (ampproject#13009)

* Disable ampCors for analytics remote config XHR in a backward compatible way.

* Fix test
protonate pushed a commit to protonate/amphtml that referenced this pull request Mar 15, 2018
…ble way (ampproject#13009)

* Disable ampCors for analytics remote config XHR in a backward compatible way.

* Fix test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AMP-Analytics: Errors with Google Tag-Manager
4 participants