Hacker News new | ask | show | jobs
by cloud_thrasher 2560 days ago
From my experience, it's the "Access-Control-Allow-Origin: *" response header that causes the problem. So, it's in the way Chrome uses/enforces cross-origin HTTP request/response headers.