Pages bug: foo.bar.html not accesible

Not sure if this is the right place for bug reports.

It seems that if a .html has a “.” (dot) in the name, it cannot be accessed.

For example: https://sumatrapdf.pages.dev/test.page.html

This should show this page: sumatrapdf/test.page.html at master · sumatrapdfreader/sumatrapdf · GitHub

Instead, it re-directs to https://sumatrapdf.pages.dev/test.page (which strangely returns 200 but no response) and then somehow goes to my default page /free-pdf-reader.html (presumably because I redirect / there via sumatrapdf/_redirects at master · sumatrapdfreader/sumatrapdf · GitHub)

It should just show the content of test.page.html file. A dot (".") is valid in url.

I converted my website from Netlify and Netlify didn’t have problems with such files.

It looks like a bug in how Pages handles files like “test.page.html”.

I haven’t tested other “weird” characters but maybe would be a good idea to add a test that Pages properly handles all valid characters in the URL i.e. -._~:/?#[]@!$&'()*+,;

That does surprise me since it’s not uncommon to have filename.min.css

You might check with the Workers dev team at Discord:

My theory is that this is caused by a bug in /foo.html => /foo redirect logic.

Therefore this wouldn’t apply to non-html files, like .css files.

Possibly after they redirect /foo.bar.html => /foo.bar, they still see a . in the name so they cut the .bar “extension” again and try to read from foo.html, which doesn’t exist so they then do 404 logic which bounces to /.

I’ve added 404.html to my website so now https://sumatrapdf.pages.dev/test.page serves my 404.html page instead of redirecting to / as in my original report.

Still a bug.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.