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
According to HTTP Caching RFC, requests containing Authorization header should not be cached, unless several special directives (must-revalidate, public and s-maxage) explicitly allow it.
And in current implementation request containing Authoirization header is cached despite the response contains header Cache-Control with value max-age=7200 (no directives allowing caching of authenticated requests).
According to HTTP Caching RFC, requests containing
Authorization
header should not be cached, unless several special directives (must-revalidate
,public
ands-maxage
) explicitly allow it.And in current implementation request containing
Authoirization
header is cached despite the response contains headerCache-Control
with valuemax-age=7200
(no directives allowing caching of authenticated requests).Middleware configuration:
Request headers:
Response headers:
Possibly, implementation should be adjusted to RFC, or this discrepancy should be documented.
Thanks a lot.
The text was updated successfully, but these errors were encountered: