🐛 Bug - Uppercase URL paths fail to load due to forced lowercasing

Requested by: @amankumarrr via YakShaver.ai 🦬
cc: @amankumarrr, @Calinator444, @brookjeynes-ssw, @adamcogan, @babakamyljanovssw

Hi Team!

  🟥  Watch the video (1 min 33 sec)

  Url from screen share: https://app-sswwebsite-9eb3-staging.azurewebsites.net/consulting/AI-Powered-Phone-system

Pain

On the ⭐ SSW Website (Dev - Next.js), pages fail to render when a user navigates to a URL containing uppercase characters in the path. This is caused by a Cloudflare transformation rule that forces all URI paths to lowercase. Since Next.js routing is now case-sensitive, lowercasing the path results in routes not being found. The Cloudflare rule should be disabled or updated, or an alternative fix implemented, to ensure uppercase and lowercase URLs resolve correctly.

Acceptance Criteria

1. Pages load correctly when accessed using uppercase, lowercase, or mixed-case URL paths.
2. Cloudflare no longer forces all URI paths to lowercase, or an equivalent fix is implemented.
3. Next.js routing behaves consistently with the deployed Cloudflare configuration.
4. No regression is introduced for existing lowercase URLs or static assets.
5. The fix is verified on the SSW Website (Dev - Next.js) environment.

Reproduce Steps

1. Navigate to the SSW website using a URL with an uppercase character in the path (e.g. https://www.ssw.com.au/Consulting).
2. Observe that the page does not load or shows no content.
3. Change the same URL path to all lowercase (e.g. https://www.ssw.com.au/consulting).
4. Observe that the page loads correctly.

Screenshot

Figure: Uppercase URL paths render blank due to forced lowercasing

No repository files are named; start by checking the Cloudflare transformation rule and the deployed Next.js routing configuration for the SSW Website Dev environment. Reproduce the issue with uppercase, lowercase, and mixed-case paths, then verify that all resolve correctly without regressing lowercase URLs or static assets.