ANAYIL GROUPHosting · My Domains Submit a Ticket
Help center
HomeWeb Performance Optimisation (WPO)[WPO-011] Fix a CDN cache key fragmented by query parameters
Web Performance Optimisation (WPO)7 min•Difficulty: Avanzado

[WPO-011] Fix a CDN cache key fragmented by query parameters

Reduce unnecessary variants without mixing content that genuinely depends on the query.

Ingeniería de Rendimiento AnayilUpdated: 2026-10-10

Apply this guide to your situation

This answer covers “[WPO-011] Fix a CDN cache key fragmented by query parameters”. Read it with the summary and confirm that the symptom and service match what you are experiencing. Available options can vary by plan and account setup.

  • Before changing anything, note what you expected, what happened and roughly when. Check whether the issue affects one page or the whole service.
  • Save the full error message and note recent changes. Hide passwords, access codes, personal data and keys before sharing screenshots or logs.
  • If a step requires administrator access, restarting services or editing server files, stop if you do not administer that server. Send support the service name, error and checks you have already made.

L3 technical diagnosis

Performance / configurationSeverity: Medium; high if conversion or availability is affected

User symptoms

The CDN reports few HITs and many copies of the same page with campaign parameters.

Observed code or message

Low cache-hit ratio; repeated `MISS` for `utm_*` parameters

Likely root cause

The cache key may include every tracking parameter, fragmenting identical content. Removing functional parameters such as search, locale or variant indiscriminately can serve incorrect content.

Likely-cause and resolution matrix

Follow a branch only when evidence supports it. A symptom may have more than one cause; do not change layers by guesswork.

01Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

02Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

03Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

04Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

05Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):
bash
Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

Prerequisites

  • Authorised access to the affected site, repository or service metrics.
  • A reproducible URL and timestamp; use staging for infrastructure changes.
  • A backup or rollback method for configuration and deployments.

Important warnings

  • Inspection commands do not authorise production changes. Do not run load tests or global purges without an approved plan.
  • Never store private responses in shared caches. Server changes in Anayil Panel depend on the controls available for the service and may require its administrator/provider.

Step-by-step walkthrough

1. Reproduce and narrow the issue

The CDN reports few HITs and many copies of the same page with campaign parameters. Compare observed keys and responses for equivalent URLs with each parameter. Verify which query parameters actually change the HTML.
bash
for u in 'https://example.com/page' 'https://example.com/page?utm_source=test' 'https://example.com/page?lang=en'; do curl -sSI "$u" | grep -iE '^(HTTP/|age:|cache-control:|x-cache:|vary:)'; done
Expected output:
Low cache-hit ratio; repeated `MISS` for `utm_*` parameters

2. Apply the appropriate correction

Ask the CDN operator to normalise only approved analytics parameters while retaining locale, search, currency or filters that change results. Roll out on a non-critical route first and purge old variants.

3. Verify the experience

Requests with and without tracking share cache when their representation is identical; functional variants remain separate and return correct content.
Expected output:
The improvement is reproducible on the affected route and profile with no new functional errors.

Troubleshooting & Solutions

Low cache-hit ratio; repeated `MISS` for `utm_*` parameters

Root cause: The cache key may include every tracking parameter, fragmenting identical content. Removing functional parameters such as search, locale or variant indiscriminately can serve incorrect content.

Resolution: Ask the CDN operator to normalise only approved analytics parameters while retaining locale, search, currency or filters that change results. Roll out on a non-critical route first and purge old variants.

Rollback and recovery plan

Roll back only the changed directive, dependency or release using the recorded value. If 5xx errors, data exposure or session failures occur, have the operator disable the new rule and retain redacted logs for analysis.

Related runbooks in this category:

Was this technical guide helpful?

Facing a production outage?

Hosting Anayil system administrators can directly intervene on your server infrastructure.

Open Support Ticket at Hosting Anayil