Describe the bug
When accessing a URL with a path directly in the browser, such as https://nepali-calendar-p3ysqzfcv-posk.vercel.app/calendar/2081/7, the page returns a "Not Found" error. This issue occurs because the project is a Single Page Application (SPA), and the server is not configured to handle direct path requests.
To Reproduce
Steps to reproduce the behavior:
- Copy and paste the link with a path (e.g.
https://nepali-calendar-p3ysqzfcv-posk.vercel.app/calendar/2081/7) into the browser's address bar.
- Press Enter.
- You will see a "Not Found" error instead of the expected page content.
Expected behavior
When navigating directly to a URL with a path, the page should display correctly as it would if navigating within the application itself. The server should serve the index.html file, allowing the client-side routing to handle the path.
Screenshots
Desktop (please complete the following information):
- OS: Windows 11
- Browser: Edge
Additional context
This issue is typical with SPA projects when server-side routing is not correctly configured to redirect all requests to index.html. A potential fix would involve setting up redirects on the server or updating the deployment configuration (e.g., Vercel, Netlify) to handle SPA routing properly.
Describe the bug
When accessing a URL with a path directly in the browser, such as
https://nepali-calendar-p3ysqzfcv-posk.vercel.app/calendar/2081/7, the page returns a "Not Found" error. This issue occurs because the project is a Single Page Application (SPA), and the server is not configured to handle direct path requests.To Reproduce
Steps to reproduce the behavior:
https://nepali-calendar-p3ysqzfcv-posk.vercel.app/calendar/2081/7) into the browser's address bar.Expected behavior
When navigating directly to a URL with a path, the page should display correctly as it would if navigating within the application itself. The server should serve the
index.htmlfile, allowing the client-side routing to handle the path.Screenshots
Desktop (please complete the following information):
Additional context
This issue is typical with SPA projects when server-side routing is not correctly configured to redirect all requests to
index.html. A potential fix would involve setting up redirects on the server or updating the deployment configuration (e.g., Vercel, Netlify) to handle SPA routing properly.