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
Sometimes it is required to use the same cached version even URL is not the same for particular 2 requests. for example, Google Search Ads adds a query parameter to the URL which is different for each request but the content of the page is the same
Solution
As a solution, it is possible to add a boolean that says to ignore query parameters for a route. additionally, there can be an array of query param names that can specified not to be ignored in case of query param based pagination for example.
The text was updated successfully, but these errors were encountered:
I add to this both google ads, linkedin, facebook, etc. in some publication it adds a query param in front of it which could end up saturating the cache whether in the file system or redis or others.
It would be good to take it into account
Problem Solved By The Feature
Sometimes it is required to use the same cached version even URL is not the same for particular 2 requests. for example, Google Search Ads adds a query parameter to the URL which is different for each request but the content of the page is the same
Solution
As a solution, it is possible to add a boolean that says to ignore query parameters for a route. additionally, there can be an array of query param names that can specified not to be ignored in case of query param based pagination for example.
The text was updated successfully, but these errors were encountered: