The development environment is
server OS:Raspberry Pi OS
server side:Python(Django)
client side:HTML+JavaScript
You are creating a website that requires password login.
If the operation is not performed for a certain period of time, it is forced to log out.
Inside the website, there is a screen where you can import/export files.
Currently, even if you leave the file dialog running during import,
If no operation is performed for a certain period of time, you will be forced to log out.
In that case, the file dialog will be left open.
I thought this movement might be strange, but what kind of movement is good in general?
(Do you often choose not to log out until the import is complete?)
If you leave the file dialog open during import, but no operation is performed for a certain period of time, you will be forced to log out.In that case, the file dialog will be left open.I thought this movement might be strange, but what kind of movement is good in general?
I don't know what the authentication system the questioner is using...
For example, if you put a common authentication ticket in a cookie and exchange it, and the authentication ticket has an expiration date, and it expires, it shouldn't matter.
For example, if the authentication ticket expires after the user logs in for a long time, the browser will display the same screen when the user leaves the seat.While the user is away, the server cannot check the expiration date and change the screen if it has expired.
It doesn't matter if you think it's strange.
© 2024 OneMinuteCode. All rights reserved.