500 CORS Error With Certain Pulse Reports

Pulse reports CSS/JS load times for a project, if that project has a large amount of CSS/JS files the service throws a 500 error and reports a CORS violation.

It appears that a machine in the server pool is unable to process the large JSON file being sent on certain occasions, because a 500 error is thrown form a remote, the browser interprets it as a CORS violation due to missing header information.

---

Hi Marcin,

Sounds like the API might not be sending the CORS headers when there's an error. I'll get one of the guys to look at this and get back to you.

Cheers,
Jamie

---

Hi Marcin,

Just to let you know where this is at - looks like the error was happening outside of our API, so we weren't getting a change to set any CORS headers. We use Amazon Web Services, and their Load Balancer tool doesn't let you set headers so we can't do much about that. We have identified the issue that caused the errors in the first place (one API node was filling up its disk with log files which caused a number of hard failures) and solved it, so you shouldn't see them any more. Let me know if you're still having trouble.

Cheers,
Jamie

---