In the Designer 2.0 Web app, we observed an issue where images were not loading in certain browsers after a while. Interestingly, the same images loaded correctly during the initial attempts but later failed.
Upon investigating and comparing the network requests in Chrome, we found that in the failing cases, Chrome was not sending the Origin header in the request. Due to the absence of this header, the S3 server was rejecting the request with a CORS error.
Our research indicated that the browser was caching the image URL and, as a result, skipping the standard request flow it followed the first time. While disabling cache manually in the browser solves the problem, it’s not a viable solution to expect from end users.
Solution:
To address this, we introduced a configurable option in Designer that allows disabling cache for specific ImageView components. By default, this setting is disabled, but users can enable it based on their use case.
After applying this configuration and disabling cache for the affected ImageView, the issue no longer appeared.
