Details
-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
None
-
None
-
None
Description
Find out why response is sometimes already committed when serving CachedError ... and more interestingly why page is displayed correctly in such case (browser cache kicking in? )
While this doesn't cause any obvious issue, it might be actually hiding some flow in logic of cache handling.
Checklists
Acceptance criteria