The issue asks whether to add route protection to prevent users from accessing authenticated routes after logout via the back button. The repo is a JWT tutorial; likely the app lacks middleware to check JWT on protected routes. Research the current middleware structure in the repo, especially files like 'server.js' or 'routes.js', and consider adding a check that verifies JWT on each request. Maintainer input is needed on desired behavior (e.g., redirect to login).
do we add our own route protection? · dwyl/learn-json-web-tokens#59 | Good First Issue
