Pages like flightschedule, automatedcommandsequence, livecommands, and logs are still accessible without login by going directly to their URL. Though this is not really a security issue as their API calls require an authentication token, they become unresponsive when a user accidentally visits these pages without being logged in.
Interacting with the page (eg: send a command, submit a flight schedule, etc.)
Website shows no indication of why it isn't working but the Network tab in DevTools indicates that an authentication token is needed
Expected Behaviour
When these pages are visited without a valid login, it should instead redirect back to the homepage and alert the user that they aren't login (the alert can be done with a Snackbar + Alert component from MaterialUI to keep design consistent).
Bug Description
Pages like flightschedule, automatedcommandsequence, livecommands, and logs are still accessible without login by going directly to their URL. Though this is not really a security issue as their API calls require an authentication token, they become unresponsive when a user accidentally visits these pages without being logged in.
To Reproduce
Steps to reproduce the behaviour:
Expected Behaviour
When these pages are visited without a valid login, it should instead redirect back to the homepage and alert the user that they aren't login (the alert can be done with a Snackbar + Alert component from MaterialUI to keep design consistent).