You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XLT does not behave exactly like browsers when it comes to caching resources and revalidating expired resources. In particular, XLT takes the "no-cache" directive literally and re-requests such resources while browsers perform a conditional get to revalidate the resource.
The text was updated successfully, but these errors were encountered:
* * cache responses even if they are marked with "no-cache" or are already expired (they will be revalidated before next use)
* fixed calculation of expiration time
* adjusted test cases accordingly
* feedback from reviewer
* Ignore "must-revalidate" for now. It makes only sense together with "max-age", and if a resource has reached its max age, it will be re-validated anyway.
XLT does not behave exactly like browsers when it comes to caching resources and revalidating expired resources. In particular, XLT takes the "no-cache" directive literally and re-requests such resources while browsers perform a conditional get to revalidate the resource.
The text was updated successfully, but these errors were encountered: