Robert,

I apologize, the issue was mine and one I feel I should have been more
aware of.

Sessions are being managed via communication with a frontend MVC
(angular) and when sessions are deleted via logout, the http header is
set to send a 204 response with no body. Little did I realize, setting a
204 response means that either:

   - TeraScript/Apache drops any and all content sent, including cookies OR
   - The browser does not examine any information sent with a 204
response (including cookies.)

So the browser was never receiving the updated cookie expiry/values I
was trying to send.

Leaving request$httpheader to the default state fixed the problem.

Thanks,
-Ian

On 07/28/15 08:25, Robert Shubert wrote:
> Ian,
>
> I did a quick test and couldn't reproduce your issue.
>
> <@CALC len(<@VAR cookie$whatever>)> returns 0
>
> Please make up a test case - a TAF/TML that sets the cookie, then "unsets" 
> the cookie, then tests the cookie that shows the problem and email it to 
> [email protected].
>
> Thanks,
>
> Robert
>
> -----Original Message-----
> From: Ian Evans [mailto:[email protected]]
> Sent: Monday, July 27, 2015 7:12 PM
> To: [email protected]
> Subject: TeraScript-Talk: Cookie Expiry
>
> Hello,
>
> I am trying to set some session information in the user's cookies. When the 
> session is deemed expired (user logs out, session expiry recorded in the 
> database has passed, etc.) I set the desired cookie vars to empty values, and 
> set the expiry to "Now" per the recommendations under <@PURGE> in the 
> programmer's reference.
>
> After doing this, the value becomes uncomparable. So when I go to check for 
> empty values in the cookie vars:
>
> LEN(<@VAR cookie$some_var>) and LEN(<@VAR cookie$some_other_var)
>
> they both pass, where before the cookie existed, they failed (as expected.)
>
> Since they are set to empty values, I am puzzled at this behavior, because 
> even if they exist but are empty strings, LEN('') should still evaluate to 
> false.
>
> Even more puzzling is that when I set the values to "null" and try to catch 
> them that way, they are still uncomparable:
>
> <@VAR cookie$some_var> != 'null'
>
> returns true, even though <@VAR cookie$some_var> is set to 'null'.
>
> So because of this peculiar behavior, I am unable to distinguish these zombie 
> cookies from valid cookies. Is there something I'm not doing right?
>
> Thanks,
> -Ian
>
> PS: Thanks for all the help lately. I know I've been posting a lot recently, 
> and you folks have been very helpful.
>
>
>
> ----------------------------------------
>
> To unsubscribe from this list, please send an email to 
> [email protected] with "unsubscribe terascript-talk" in the body.
>
>
>
>
> ----------------------------------------
>
> To unsubscribe from this list, please send an email to 
> [email protected] with "unsubscribe terascript-talk" in the body.
>
>



----------------------------------------

To unsubscribe from this list, please send an email to [email protected] 
with "unsubscribe terascript-talk" in the body.

Reply via email to