Menu

#83 Navigation after Log Out gives SQL errors in nav bar

closed-fixed
MartyD
3
2009-07-25
2009-07-20
MartyD
No

After logging out, using any of the picks in the left-hand navigation menu results in the display of a SQL exception about 'x' not being a valid integer, just below the search/advanced search box.

Discussion

  • MartyD

    MartyD - 2009-07-20

    This is happening because the logout process sets the three cookies -- isfdbUserId, isfdbUserName, and isfdbToken -- to 'x' and intends to set a past expiration so that the browser will no longer deliver them. But the expiration date is not in a valid cookie date format and isn't parsing, so the cookies don't get expired (the expiration date is ignored). One ends up with a session with cookies for user 'x', id 'x'. That 'x' is then used to look up the user by id in the database, giving the SQL exception.

     
  • MartyD

    MartyD - 2009-07-20
    • priority: 5 --> 3
    • assigned_to: nobody --> marty-d
     
  • MartyD

    MartyD - 2009-07-21
    • status: open --> open-fixed
     
  • MartyD

    MartyD - 2009-07-21

    This is fixed the the commit of common/login.py 1.4 on 20-Jul-2009. Modified the cookie setting and clearing functions to use the cookie-standard date format. This causes the cookies to be expired and not delivered. As a back-up, also modified GetUserData to check for isfdbUserID and isfdbToken with values 'x' and to treat this as no-cookies/not logged in ("clearing" the cookies sets the values to 'x').

     
  • Ahasuerus

    Ahasuerus - 2009-07-25
    • status: open-fixed --> closed-fixed
     
  • Ahasuerus

    Ahasuerus - 2009-07-25

    Fixed in r2009-13.

     

Anonymous
Anonymous

Add attachments
Cancel