🐛 BUG: Getting 404 on URL that contains a dot and no trailing slash

[rcdailey]

Which Cloudflare product(s) does this pertain to?

Pages

What version of Wrangler are you using?

cloudflare/pages-action@v1

What operating system are you using?

Github Actions

Describe the Bug

I originally posted about this in the Cloudflare community forum.

I host my Docusaurus documentation site on Cloudflare Pages, and I use Algolia Crawl to index the site content for my search functionality.

If you do a GET on https://recyclarr.dev/wiki/upgrade-guide/v5.0, you will see it returns a 404. If I add a slash to the end, I get a 200. Weirdly, even though it returns 404 the page is still served and rendered correctly in my browser. However, a non-200 response breaks Algolia Crawl.

I suspect that the . character in the URL is causing an issue, because I do not get 404 responses for other pages without the dot. To me, this indicates a bug that should be fixed. I expect that the URL linked above should return 200 without a trailing slash at the end.

Additional Information

My docs site is open source and may be located here: https://github.com/recyclarr/wiki

I do not use Wrangler or anything. I build and deploy my site using a Github Workflow

[erictor]

Very interested to see if you get response and info on this. Seeing the same issue. It doesn't happen in development in the local dev server environment, but only after publishing. What might be happening is an assumption, somewhere, that if there is a period in the last segment of a URI that it must be a request for a file rather than being a route. If that's what's occurring, I'd like to think there ought to be a way to set a setting to stop that behavior.

I may be usurping by speaking of my own version of this issue, I now see, because while my website does get benefit from Cloudflare, hence Cloudflare notified me in email of the Community Forum post on this, I am not using workers-sdk. My site is a SPA app that contains routes like https://mydomain.com/routewith.period - and it does have the same behavior where if a slash is appended to the URI, navigation occurs as expected, but without the ending slash, an HTTP 404 results.

[JacobMGEvans]

@cloudflare/pages should this be in the cloudflare/pages-action repo?

[GregBrimble]

Here's probably the most appropriate, actually. If it's in any open-source code, it'll be pages-shared. But given the report suggesting that it's only affecting production, it may be something that's internal. We'll keep this issue here and take a look.

[JacobMGEvans]

Thanks @GregBrimble 😃

[rcdailey]

Hey folks. Any idea where this one falls on the roadmap / priority list? I'm guessing the affected audience for this one is low. Let me know if there's anything I can do to help get to a resolution.

[erictor]

MS PLEASE give us a way to allow for this, and furthermore, allow for it by setting a config such as in web.config, so that one could do it if one was on a hosting plan and did not have direct access to IIS host settings. For example, on Instagram they allow usernames that include a period within, like my.username, and the user's account becomes accessible with instagram.com/my.username. I would like to implement similar functionality. I attempted to use a Regex in web.config to allow for this when the request is not a file but it not only failed, it caused other worse issues to occur.