Jump to content

Is this a good idea? (Sessions & Cookies manipulation) read


Demonic

Recommended Posts

I was wondering since sessions don't work well with applications (logging in from a program to download data from a website doesn't allow the session to be persistent) So I was wondering if I should set a cookie based on the current session id, store that session in the database with the current time.  Then I can manipulate my script to delete sessions after so long to make them re`login, that way I can use my python program to login yet it will log them out in a certain time(possibly 24 hours or less).

 

So, is it a good idea to store current session in db with the current time and in the users table, then store that session in a cookie to stay logged in then delete the cookie in db, and if that session no longer exists in the database they have to re`login.

By default, the session id is stored in a cookie. To hold the session, when the user logs on, send the session ID back to the application, and just call the pages as:

 

page.php?PHPSESSID=sessionid

 

When the session id expires, have the php page send that information back to the application

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.