Details
-
Type:
Bug
-
Status: Closed
-
Priority:
P2: Important
-
Resolution: Done
-
Affects Version/s: 6.x
-
Fix Version/s: 6.3.0 Feature Freeze
-
Component/s: Network: HTTP
-
Labels:None
-
Platform/s:
-
Story Points:5
-
Commits:4757b93b0ef149a3564582a45589f731755c4236
-
Sprint:Team 2 Foundation_Sprint 41
Description
As revealed by QTBUG-95950, some cases are not covered and need to be tested to prevent future regressions.
The various cases are:
- The cache is empty (already tested)
- The cache is not empty, and the currently inserted entry would be the new last-to-expire node in the cache (called "newest")
- The cache has at least two elements and the currently inserted entry is set to expire between the two.
- The cache is not empty, and the currently inserted entry is the new next-to-expire node in the cache (called "oldest")
Attachments
Issue Links
- relates to
-
QTBUG-95950 QNetworkAccessCache crash
-
- Closed
-