Having trailing slash in the blog path, results in 404
See original GitHub issueThe other pages, like talks
, have no issue with this
Note that the first result in the google for your blog, uses trailing slash
Issue Analytics
- State:
- Created 5 years ago
- Comments:20 (19 by maintainers)
Top Results From Across the Web
trailing slash results in 404 error page CSS not working
I've set up a 404 error page so that visitors with bookmarks to now non-existent pages or pages whos names have changed can...
Read more >Trailing slash endpoint routing returns 404 · Issue #346 - GitHub
If the route defined in the Swagger spec already has a trailing slash (probably due to human mistake), normalize it first and process...
Read more >Should You Have a Trailing Slash at the End of URLs? - Ahrefs
A trailing slash is a forward slash (“/”) placed at the end of a URL such ... nothing after this path, usually a...
Read more >[Help] Trailing slash results in 404 : r/reactjs - Reddit
When I visit my url with a trailing slash it works fine but when I leave it out I get a 404 back....
Read more >PM34409: Trailing slash in URL results in HTTP 404 - IBM
HTTP requests that refer to a friendly URL that contains a trailing slash (/) result in status code 404.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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 💜