# Event website redirect-loop trace and repair sheet (English)

Use this sheet for one **public GET page** that shows “too many redirects.” Do not test by repeating a form submission or purchase. Ask the website or ticketing owner for a safe provider-specific diagnostic if the failure starts inside checkout.

## Visitor impact and temporary route

| Field | Evidence / decision |
| --- | --- |
| Failing public host, path, language and safe query-parameter names; redact token-bearing values | |
| Browser error, device, time and screenshot | |
| Affected attendee task (event facts / registration / tickets) | |
| Verified direct destination, if available | |
| Approved visitor update channel and support owner | |
| Fresh-browser or second-device comparison | |

## Redirect chain: copy actual response evidence

Record a short, bounded number of hops. Stop at a repeated URL, a final page or the last observed hop if no URL repeats. Use safe URL shapes in this shared sheet; keep full token-bearing URLs only in the owner's restricted diagnostic system. Do not paste attendee details.

| Hop | Requested scheme + host + path | HTTP status | Redacted `Location` destination, if any | Serving layer or owner | Evidence time |
| --- | --- | --- | --- | --- | --- |
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
| 4 | | | | | |
| 5 | | | | | |

First repeated URL and hop, or last observed hop at the trace limit: ____________________

Compare at each hop: `http`/`https`; `www`/apex; old/new domain; language path; trailing slash; safe query-parameter names. Check recent rules at CDN/edge, host/origin, CMS/application and language router. Identify the rule that actually emitted the conflicting `Location`; a DNS answer alone does not identify it.

## One approved change

| Field | Record |
| --- | --- |
| Confirmed conflicting rule and owner | |
| Intended final URL and expected status | |
| Existing rule/configuration saved by owner | |
| Reviewed scoped correction | |
| Reversal method and decision owner | |
| Publish/change time | |

Do not weaken TLS, turn off HSTS or remove unrelated redirects to see whether the error disappears. If two providers own adjacent hops, have them review the same chain before changing either side.

## Published visitor retest

| Entry point | Intended event edition, language and final URL | Actual final URL/status | Phone | Desktop | Owner/time |
| --- | --- | --- | --- | --- | --- |
| Old announcement link | | | | | |
| New event homepage | | | | | |
| Event detail or programme | | | | | |
| Ticket/registration button (stop before purchase) | | | | | |
| Other language route | | | | | |

Record a new redirect trace for the original failing URL. Close only after it reaches the intended page without cycling and the affected attendee task is usable. Update controlled emails, QR destinations and partner links that still point to the broken route.