I exactly ran into this issue when migrating from a different provider to CF pages. I preferred to strip away the .html extensions anyway, so it was okay in my

I exactly ran into this issue when migrating from a different provider to CF pages. I preferred to strip away the .html extensions anyway, so it was okay in my case. CF should trigger a HTTP 308 for older .html to the new urls automatically.