Your backend file server that is actually serving up your JS files needs to
understand what paths are considered your "frontend" and always serve your
index.html when it gets requests against any of those paths. This is what
the OpenShift console itself does. In the 3.x openshift console it was in
Anyone? I bet it's a common use-case (Angular, React.js frontend apps),
can't be that nobody has had this issue...
Regards,
Pavel Maslov, MS
On Thu, May 9, 2019 at 10:50 AM Pavel Maslov
wrote:
> Hi all,
>
>
> I have a React.js single-page app deployed to Openshift that uses its own
> router
Hi all,
I have a React.js single-page app deployed to Openshift that uses its own
router (e.g. /home, /about, /photos, etc.). Everything works fine (user
navigating around my app) until the user refreshes the page. This in turn
fires a GET request to the server, which it of course cannot resolve
