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

Add bing-amp.com to the list of AMP Cache hosts #1447

Merged
merged 3 commits into from
Nov 15, 2018
Merged

Conversation

westonruter
Copy link
Member

See https://blogs.bing.com/Webmaster-Blog/September-2018/Introducing-Bing-AMP-viewer-and-Bing-AMP-cache

The AMP protocol offers the ability to cache and serve cached copied AMP content that is published on the web, providing faster user experiences on Bing. In order to enable your AMP published content within Bing, you need to allow the Bingbot (our crawler) to fetch AMP content and allow cross-origin resource sharing (CORS) for bing-amp.com domain. Most AMP enabled sites and advertisers have already authorized the CORS sharing for the ampproject.org domain, but now need to also bing-amp.com to the allowed list.

Nevertheless, I'm not sure if it is supposed to be https://bing-amp.com or https://www.bing-amp.com, as the former name does not resolve but the latter does.

@westonruter westonruter added this to the v1.0 milestone Sep 19, 2018
Copy link
Member

@amedina amedina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome Bing Cache!

@westonruter
Copy link
Member Author

Let's wait to merge until we get confirmation on www.bing-amp.com vs bing-amp.com.

@westonruter
Copy link
Member Author

@westonruter westonruter changed the base branch from develop to 1.0 November 15, 2018 15:32
@westonruter westonruter merged commit d769a64 into 1.0 Nov 15, 2018
@westonruter westonruter deleted the add/bing-amp branch November 15, 2018 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants