Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
When the main minified JS for the CMS UI cannot be loaded via the script proxy a meaningful HTTP status code (e.g. 404) is returned and an error is logged.
When the main minified JS for the CMS UI cannot be loaded via the script proxy a 200 HTTP status code is returned with the file being empty. That leads to a broken UI after login and the reason for this is quite hard to debug, because of the 200 status code and only shows in form of follow up errors in the browser console
Steps to reproduce
Btw, are there any plans to get rid off the script proxy and the lazy generation of the core JS?