old-kentcdodds.com: Having trailing slash in the blog path, results in 404

I think we can close this now. If I hear reports from others that they’re having this issue I’ll raise it again and we can dig deeper. Thanks everyone!

@dimitrisnl this doesn’t really seem like a broken link, though. I’m not sure if anyone else has been able to reproduce, which is unfortunate.

Long shot - but maybe disable all your extensions (I saw some type of ad blocker at least)? It’s possible something is conflicting and causing issues with the service worker. The Google Analytics script sometimes gets blocked–wondering if that has anything to do with the error here?

Also perhaps it’s a bug in your version of Chrome? Try updating?

Finally - perhaps there’s something helpful in the console logs. Could you try opening your console, enabling Preserve Log, and then seeing if any errors arise there?

It’s very difficult (as Kent notes) to pin this down when we can’t reproduce it. This doesn’t seem like a wide-spread issue, but still unfortunate you’re experiencing this!

Also PS: thanks for using Gatsby on your personal site 💜

@kentcdodds I think that’s probably more likely than Netlify failing with CDN/redirecting trailing slashes–that seems like behavior that would be unlikely to break.

For some context, the awesome @davidbailey00 wrote a good chunk of the gatsby-plugin-offline code, so thanks for that David!

@dimitrisnl could you shed any light on reproduction steps to trigger this flow? Maybe David’s comment above is helpful?