Home
Support Forums

Netlify SSR Does Not Support URLs with "." (a dot or a period) in the URL

Hi there,

This has been a pain to debug today, but I think I have reached the bottom of the issue.
I am using server-side rendering with Netlify (the default SSR used when enabling it in settings).
I’m using it with React Helmet for dynamic metatags.

My site is focused-chandrasekhar-24a072
I have it hosted at hyaliko.com

I use react-router-dom to take any path of the form

https://www.hyaliko.com/

and route it to the same page.

So hyaliko - the social spatial nft gallery and hyaliko - the social spatial nft gallery both navigate to the same page.
The dynamic metatags work for those paths.

My issue is that when paths look like this “hyaliko - the social spatial nft gallery” the dynamic meta tags don’t load at all.

I have narrowed down the issue with 99% confidence and I’m pretty sure that the issue is the “.” in the last part of the path.
If I remove the dot and type in any other word or series of characters, it works fine, but as soon as they’re separated with a dot, it breaks.

Here’s some screenshots using Twitter’s OpenGraph tag debugger to illustrate

And to be clear, the app works totally fine, the only thing that doesn’t work is loading metatags through Netlify’s SSR. So I’m thinking that there might be something going on with the SSR where it does not handle paths that include dots (".").

This is actually a very pressing issue for me as I can’t change my URL schema and the only fix would be to migrate to a different platform.

Thanks in advance for the response!

Best,
Collin McKinney

Here’s the second screenshot

You’re not wrong - our prerendering service has a bug where files with dots in the name are not handled correctly:

So, if you use our prerendering service (which feeds facebook, twitter, slack, pinterest, etc) to generate your OG data, you’ll find paths like that don’t work well for that application and you should aim to avoid them for now if you require good prerendered output.

oh wow, thanks for linking that issue! I hadn’t seen it.

Is there any sort of timeline on this issue being fixed at all? I know prerendering is still in beta, is it being worked on?

Would love info on this so i can decide whether to switch to an external pre-rendering service, because having dots in my URL is unfortunately a must :frowning:

I don’t have any timeline for this fix, unfortunately. I know it is not likely to happen in the next couple of months.

I also know that is not the answer you were hoping for, but I do want to be transparent since while I cannot fix the codepaths, I can at least help you plan for your business’ needs.

Unfortunately - the same thing is likely to happen with an external prerendering service by my understanding. It’s pretty easy on our side to enable prerender.io or prerender.cloud if you want to do a quick test (but I don’t have an account at either to test on, myself). We do need the API token which you should not post publicly if you do decide to do that test. I’d suggest a separate site since we can’t activate the setting - only configure it, and it gets activated with your next deploy (and then you can’t change it, only we can) - so best to isolate it during testing is my advice.