Skip to content
This repository has been archived by the owner on Jun 11, 2022. It is now read-only.

Directly going to non root route on first load = 404 #123

Closed
rolandpeelen opened this issue Sep 3, 2018 · 2 comments
Closed

Directly going to non root route on first load = 404 #123

rolandpeelen opened this issue Sep 3, 2018 · 2 comments

Comments

@rolandpeelen
Copy link

I started using the buildpack and I have this app running that works fine with the regular (non builded version) when just pushing to heroku. Unfortunately, with the buildpack, when going directly to a url that is not the root (ie /x/:id for instance), I get a 404.

Example: https://bachkoor-v2-frontend-staging.herokuapp.com/events/5b88f17e551c85002c181932

This is still running a free tier dyno, might take a bit to load

Any clue as to what is going wrong?

It seems that as soon as the page is loaded once, it can resolve through the service worker, but if it hasn't been, then it doesn't fetch it properly :)

@mars
Copy link
Owner

mars commented Sep 3, 2018

Hi @rolandpeelen 😄

Did you setup URL routing?

@rolandpeelen
Copy link
Author

@mars -- Completely missed that one, so sorry. Thanks for the tip!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants