Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.7.2
-
Linux/X11
-
e4a35df2a (dev), bbfc7b2ca (6.8)
Description
As per RFC911 what it should do is if must-revalidate is set and max-age is still valid, it should serve the cached data, but it appears that Qt is doing apposite of it, that even if max-age is valid and considered fresh and if must-revalidate is there, Qt is going back to server to get the fresh data ?
Attachments
| For Gerrit Dashboard: QTBUG-128484 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 600604,3 | Http: fix how we treat must-revalidate | dev | qt/qtbase | Status: MERGED | +2 | +1 |
| 601236,2 | Http: fix how we treat must-revalidate | 6.8 | qt/qtbase | Status: MERGED | +2 | 0 |