/consultation redirects to /consultation/, then back again. Two layers are often applying opposite rules: one adds the trailing slash and another removes it.
Make both responses visible
Open the network panel with its log preserved and request the address again. Record the status and Location for each step. Request the slash variant directly as well. Once an address repeats, stop: further requests will not reveal a new destination.
Fictional example: a proxy requires a trailing slash while the framework serves pages without one. Each layer’s rule may look reasonable in isolation, but together they create a loop.
First choose which variant the application should serve directly with the intended content. Align the proxy, framework, canonical URLs and internal links with that decision.
Limit the rule to suitable routes
Image files and API endpoints do not automatically need the same treatment as content pages. Inspect existing router behaviour and restrict the change to appropriate paths.
After the correction, the preferred URL should open without a normalization redirect. The other variant may redirect there once if that is the chosen policy. Include a deeply nested page in the check: a working homepage does not show whether nested routes still loop.
Related check: Check a canonical redirect destination.
When the proxy and application disagree, the Technology and stack review helps clarify structure and responsibilities before implementation.