[MGNLCACHE-226] Improvement for download content of cached error responses Created: 17/Feb/20  Updated: 23/Jul/20

Status: Open
Project: Cache Modules
Component/s: cache browser
Affects Version/s: 5.8.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 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


Generated at Sun Feb 11 23:53:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.