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
Currently, CoreLibs only partially uses cache as it ignores If-Modified-Since in the request headers.
Proposed solution
Here's what we should do:
Send Last Modified header in the response that is equal to the time when the filtering engine was built or changed last time.
Check If-Modified-Since in the requests and depending on its value return HTTP response with status 304 instead of trying to select cosmetic rules extra time.
Alternative solution
No response
The text was updated successfully, but these errors were encountered:
Issue Details
Currently, CoreLibs only partially uses cache as it ignores
If-Modified-Since
in the request headers.Proposed solution
Here's what we should do:
Last Modified
header in the response that is equal to the time when the filtering engine was built or changed last time.If-Modified-Since
in the requests and depending on its value return HTTP response with status304
instead of trying to select cosmetic rules extra time.Alternative solution
No response
The text was updated successfully, but these errors were encountered: