Unexplained redirect

I am seeing an unexpected redirect to a non-existent file which seems to show the correct content.

We have a file pedalers.travel/TandC.htm which contains terms & conditions. When you go direct to that webpage you get redirected to pedalers.travel/tandc. The content of tandc is the same as TandC.htm. If you go via the website navigation you get TandC.htm (via page hydration).

There is no redirect specified in our _redirects file, there is no tandc file in the zip we upload to Netlify.

No other page on the website has this issue.

Our Netlify url is pedalers.netlify.app

You’ve linked the URL to tandc.html. Netlify normalises so that tandc.html is same as tandc. There’s no way to disable this behaviour, and personally it shouldn’t be disabled so that folks can avoid typing .htm in the address bar - much like how most websites behave.

You’ve linked the URL to tandc.html.

Not sure what you mean here, as we have no file named tandc.html, nor is there any redirect of any sort related to any name using tandc.

Our file names use .htm not .html, but it is only the TandC.htm that has the issue, none of the others exhibit this behavior.

When you load that webpage (pedalers.travel/TandC.htm), it actually shows a 301 redirect to tandc. If you load any other filename.htm it only returns a 200 to filename.htm.

Please note if you are viewing the website and use the navigation menus, you get a hydrated version of the webpage not a fresh load of the page. You need to load the page by itself to see the behavior.

pedalers.travel/tandc.htm loads fine @mrcycling

TandC.htm is forced to lowercase as per this post. Feature request to opt out here.

Naming this one file as mixed-case (TandC.htm) when all other filenames in the site are lowercase is breaking your own convention.

Never mind, just read the linked thread. Guess I have to either live with redirects or change file names to the Netlify way.

That’s why I linked to the thread.

To clarify - we will make sure that visitors to your original URL still get the content, no matter how you access it. So you can use any name you want here, but you will have to live with how we serve it - in this case, via some normalizing redirects.

(In reality, our CDN doesn’t even store filenames as mixed case - they are all lowercase - but we take requests for FILE.HTML, File.html, file.html, and file - and serve the same content for all).