making "/index.html" accessible from the browser

… to make “index.html” accessible from browser?

I’m referring to your basic sample project. Everything is working as long as I’m browsing

localhost:3000

But if I call

localhost:3000/index.html

I’m getting

404 - Oh no's! We couldn't find that page :(

That wouldn’t be a big issue for me, but I’m hosting the app using sparkjava with a Jetty server behind. And this guy seems to rewrite any empty path to “index.html” -> 404 -> boom.

Any suggestion?

[tannerlinsley]

I see what you’re saying. This is what’s happening:

• The page loads index.html just fine, and you see the simple HTML and CSS that ships on first load.
• The js is parsed and React mounts. This is when you see the 404. This happens because the route path is seen as /index.html instead of /. In fact, this exact same problem would happen if you were to use create-react-app and react-router. React router will look for a route component with path='/index.html'. When that route is not matched in the component tree, the fallback route is used, which in React Static’s case is the 404 component, naturally.

The only ill-fated way to try and get around this is to somehow register your routes using the suffix, and this simply won’t fly with react-router or the filesystem. It would attempt to create /index.html/index.html.

There are also a slew of other issue that could arise in react-router and react-static because of that change, so I wouldn’t suggest attempting this.

In the end, you will be much better off by implementing a URL rewrite in your server configuration to remove the .html suffix and /index paths from routes that match an HTML file. This may or may not help you: http://www.eclipse.org/jetty/documentation/9.4.x/rewrite-handler.html.

[pmogollons]

For anyone stumbling upon this issue, I was able to fix it using JS creating a script tag in the head with the following code

window.location.pathname === '/index.html' && window.history.replaceState('', '', '/');

This method doesnt even redirect and will not show the 404 page because the /index.html path wont be there when react loads.

Maybe something similar can be implemented in the code base of react-static or maybe just documented so that people is aware of this.

In my case it was important because google for some reason was indexing /index.html and all my clients where getting to the 404 page.