You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Login/Register" button on the /tools/sip.html page is incorrectly redirecting to /tools/loginPage.html, which causes a 400 error. The intended redirect path should be /loginPage.html without the /tools directory.
Steps to Reproduce
Navigate to /tools/sip.html.
Click on the "Login/Register" button.
Observe that the page redirects to /tools/loginPage.html instead of the intended /loginPage.html, causing a 400 error.
Expected Behavior
The "Login/Register" button should navigate to /loginPage.html instead of /tools/loginPage.html, ensuring the correct page is loaded without causing a 400 error.
Screenshots/Logs
No response
Additional Information
I agree to follow this project's Code of Conduct
I'm a GSSOC'24 contributor
I want to work on this issue
I can provide more details if needed
The text was updated successfully, but these errors were encountered:
👋 Thanks for opening this issue! We appreciate your contribution. Please make sure you’ve provided all the necessary details and screenshots, and don't forget to follow our Guidelines and Code of Conduct. Happy coding! 🚀
✅ This issue has been successfully closed. Thank you for your contribution and helping us improve the project! If you have any more ideas or run into other issues, feel free to open a new one. Happy coding! 🚀
Preliminary Check
Bug Summary
The "Login/Register" button on the
/tools/sip.html
page is incorrectly redirecting to/tools/loginPage.html
, which causes a 400 error. The intended redirect path should be/loginPage.html
without the/tools
directory.Steps to Reproduce
/tools/sip.html
./tools/loginPage.html
instead of the intended/loginPage.html
, causing a 400 error.Expected Behavior
The "Login/Register" button should navigate to
/loginPage.html
instead of/tools/loginPage.html
, ensuring the correct page is loaded without causing a 400 error.Screenshots/Logs
No response
Additional Information
The text was updated successfully, but these errors were encountered: