Geodesic Solutions Community Wiki

User Tools

Site Tools

You are here: Auction and Classified Software Support Home » How Our Auction & Classified Software Works » Advanced Topics » Sessions and Cookies
how_this_software_works:advanced:sessions_and_cookies

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
how_this_software_works:advanced:sessions_and_cookies [2010/04/28 18:26]
james created 		how_this_software_works:advanced:sessions_and_cookies [2014/09/25 16:55] (current)
Line 13: Line 13:
   * "real time" general statistics information displayed, such as the number of people currently viewing the site.   * "real time" general statistics information displayed, such as the number of people currently viewing the site.
   * List of users currently logged in (displayed in admin panel)   * List of users currently logged in (displayed in admin panel)
 +  * Keep track of the "state" of certain user interface elements, for instance to show the last tab selected or show the last browsing view selected.
 +  * If using the social connect addon, and user logs in with Facebook, used to keep track of Facebook ID and related information.
  
 This is how a new registration currently works: This is how a new registration currently works:
Line 49: Line 51:
 ==== 2.0.6 - 3.0.2 ==== ==== 2.0.6 - 3.0.2 ====
  
-This marked an "in between" stage in session handling, where it was getting better, but still had it's flaws.+This marked an "in between" stage in session handling, where it was getting better, but still had its flaws.
  
 During this period, in order to verify cookies were working, the page would re-load 3 times and after that would just accept that cookies did not work, and would display the page.  There was still no explanation to the end user however when they tried to log in.  Here is the new scenario: During this period, in order to verify cookies were working, the page would re-load 3 times and after that would just accept that cookies did not work, and would display the page.  There was still no explanation to the end user however when they tried to log in.  Here is the new scenario:
Line 58: Line 60:
   - Cookie is set, or the "redirect count" is 3 or more, so display the page.   - Cookie is set, or the "redirect count" is 3 or more, so display the page.
  
-So now, if the cookie is not set, it would redirect 3 times, then display the page.  There is a technical reason for trying 3 times but I won't bore you with the details.  This seemed to work OK but still had it's flaws.  For instance, every time the page re-directed, it created a new session, so that's 3 new sessions every time someone views the page with cookies turned off.+So now, if the cookie is not set, it would redirect 3 times, then display the page.  There is a technical reason for trying 3 times but I won't bore you with the details.  This seemed to work OK but still had its flaws.  For instance, every time the page re-directed, it created a new session, so that's 3 new sessions every time someone views the page with cookies turned off.
  
 There is still not an accurate message displayed when the user tries to log in or register when cookies are turned off, it just re-loads the page with no explanation of why things don't work.  There was also issues with some of the newer session security added, like it would force the session to have the same IP number to help make //session hijacking// harder.  That turned out to be a bad idea for certain ISP's, specifically AOL and a few others where the IP would change. There is still not an accurate message displayed when the user tries to log in or register when cookies are turned off, it just re-loads the page with no explanation of why things don't work.  There was also issues with some of the newer session security added, like it would force the session to have the same IP number to help make //session hijacking// harder.  That turned out to be a bad idea for certain ISP's, specifically AOL and a few others where the IP would change.
  
 So the developer decided to hit the drawing board again to come up with an even better solution, that would show **accurate** error messages if cookies were not working, would not require re-directing 3 times just to view the page without cookies, etc.  The result is the current way sessions are handled, which you can see in the section [[#How Sessions Work]]. So the developer decided to hit the drawing board again to come up with an even better solution, that would show **accurate** error messages if cookies were not working, would not require re-directing 3 times just to view the page without cookies, etc.  The result is the current way sessions are handled, which you can see in the section [[#How Sessions Work]].
how_this_software_works/advanced/sessions_and_cookies.1272479216.txt.gz · Last modified: 2014/09/25 16:55 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki