[MGNLCACHE-167] The 'Pragma: no-cache' header is obsolete and causes issues Created: 09/Mar/17  Updated: 25/Mar/22

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

Type: Improvement Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: quickwin, to-estimate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLCACHE-206 Remove all use of Pragma header Closed
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   

During the investigation done for MGNLUI-4126, mgeljic and I both arrived to the conclusion that the 'Pragma: no-cache' header is obsolete. It was meant for HTTP 1.0 which has been updated to 1.1 a long, long time ago. See for instance:

"I encountered an old smartphone browser that didn't support it [HTTP 1.1] about 9 years ago, but that's the last example I can think of where I'd even heard of an HTTP client that didn't."
Source: http://stackoverflow.com/questions/535053/which-webbrowsers-use-http-1-1-by-default (2009)

It is also unclear what the header was ever meant for. It would therefore make sense to try to remove it, in order to hopefully avoid more IE / legacy-software issues like the one I mentioned above.


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