![]() Great! I just have to answer to all my 404 errors with the index.html file! So that's what I did! ![]() (you see, the Vue Router guys agree with me about the uglyness of the 404 page □) If the URL doesn't match any static assets, it should serve the same index.html page that your app lives in. Not to worry: To fix the issue, all you need to do is add a simple catch-all fallback route to your server. Since our app is a single page client side app, without a proper server configuration, the users will get a 404 error if they access directly in their browser. So yes, I have done my research and read the docs, which add the solution to this problem: Let's say, for instance, that the SPA serves the home page in and another page in Navigating from the home page to the bar page runs correctly as expected, but if you try to access just copy-pasting its URL to the browser's address bar or even refreshing the page when the browser is serving it, you get an ugly 404 page (with ugly I mean it's not even styled □□). After deployment, the app is up and running correctly. I have a Vue SPA that is served from an S3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |