Throw dev error if CORS headers don't support AMP Cache
See original GitHub issueTo help publishers catch AMP CORS errors in development.
b/125944172
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
CORS in AMP - amp.dev
Verify that the CORS Origin header is an allowed origin (publisher's origin + AMP caches). If there isn't an Origin header, check that...
Read more >[AMP cache] access-control-allow-origin CORS errors · Issue ...
The response headers are great but the request headers are not. Please try adding a crossorigin parameter to your svg/img, that will fix...
Read more >CORS issue - No 'Access-Control-Allow-Origin' header is ...
My service application uses Spring MVC, Spring Data JPA and Spring Security. I have included CorsConfiguration class as shown below: CORSConfig.
Read more >3 Ways to Fix the CORS Error — and How the Access-Control ...
Fix two: send your request to a proxy The cors-anywhere server is a proxy that adds CORS headers to a request. A proxy...
Read more >Error on amp page that serve from google cache
ampproject.org'. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You probably mean to mention @sebastianbenz 😉.
/to @alabiaga Aaron, would you mind working on this?