Hi Peter,
This is an intended feature of our platform from which you cannot opt out. We’ll serve any combination of case (e.g. FiLe.HtMl or file.html or FILE.HTML) correctly, though the mixed-case ones will be redirected to the “canonical” lowercase definition.
We found that most people deploy from a non-case-sensitive filesystem (windows/mac) and this was the best way to make things work as most folks intended.
Aside from the unwanted (1-time per browser) HTTP 301 redirect, which gets cached by the browser so it is not an “ongoing cost” for repeat visitors, is there any other problem with this in your workflow (e.g. your site won’t work due to it)?