Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
5.8.1
-
None
Description
From SUPPORT-10898:
When customer provoke a cache-entry for a 404 response on our public servers, then the Cache-Browser-App is not able to download that cached response. System shown an error dialog instead of any explanation.
Investigation shown that:
Errors, such as 400, cannot be downloaded because the CachedError does not have any content stored. What is stored is status code, url, timestamp and ttl. Whereas the supported type of cache entry, InMemoryCachedEntry, actually contains the data of cached content which we're able to pull and download.
We would expected that:
1. either display proper message that content cannot be downloaded,
2. or disable download content action for all cache entries except InMemoryCachedEntry
Checklists
Acceptance criteria