Jump to content

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


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

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • 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.