-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not Found when directly accessing a link #96
Comments
how can i contribute? Since, it's hosted on vercel, it's a simple fix for now |
it's working on the main domain, only not seeming to work on preview builds. |
https://miti.bikram.io is hosted on Cloudflare, not on Vercel that's why. |
We were previously using vercel to deploy previews from Frontend, we are slowly moving to cloudflare, and vercel will no longer be used from v2 |
Cloudflare is such a good choice. I've been using it recently as well. Kudos! |
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.html
file, 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.The text was updated successfully, but these errors were encountered: