Open wezell opened 1 year ago
This issue is significantly amplified by the fact that many mail clients and mail servers pre-fetch the URLs in email messages at the time the message is received. Since these URL parameters are used in marketing emails, and email marketing campaigns send out many messages at once, this results in a flood of cache-busting Page requests from many unique IPs received in a short time span.
Cloud support incidents https://dotcms.zendesk.com/agent/tickets/114223 https://dotcms.zendesk.com/agent/tickets/114621
another incident March 2024 https://dotcms.zendesk.com/agent/tickets/115386
I guess this would be important to configure on a site by site level.
Also would be good to be able to ignore by pattern. Things like utm_*
and *clid
would take care of a lot.
User Story
Currently, our page cache takes all parameters into account when building the key for page cache. This means that common SEO type tags which get passed all the time should be ignored and should not force churn in the page cache. Examples of such params are:
Acceptance Criteria
Proposed Objective
Application Performance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Sub-Tasks & Estimates
No response