RhinoTrac
LassoSoft Ticket Tracking System
NOTE: If you are using Lasso Server 9.3 please Log your ticket directly via the LUX admin as this will give us more information about your issue.
Lasso 9 Issues
Ticket #7934: Setting cookie does not honor string expire values
- Reported by:
- Jolle
- Date:
- 12 Jan, 2015
- Priority:
- minor
- Component:
- Lasso 9
- Version:
- 9.3
- Keywords:
- Platform:
Issue Report from Jolle (jolle@kulturfaktorn.se)
Company: Kulturfaktorn
Component: Lasso 9 Server
Version: 9.3
Source IP: 90.229.223.158
Detail
======
The documentation for web_response->setCookie in regards to the -expires param states:
"Any other object type is appended directly to the outgoing cookie header string"
This does not appear to be the case.
Setting a cookie like this:
web_response -> setcookie(
'hardcoded' = lasso_uniqueid,
-expires = 'Mon, 26 Jan 2015 10:46:18 GMT',
-path = '/'
)
will result in this sent to the browser:
Set-Cookie hardcoded=414F2A7D-F4DE-4111-9E8C-A3D3DC9E1106;expires=Mon, 12-Jan-2015 10:53:12 GMT;path=/
Please log in to your LassoSoft account to comment
Company: Kulturfaktorn
Component: Lasso 9 Server
Version: 9.3
Source IP: 90.229.223.158
Detail
======
The documentation for web_response->setCookie in regards to the -expires param states:
"Any other object type is appended directly to the outgoing cookie header string"
This does not appear to be the case.
Setting a cookie like this:
web_response -> setcookie(
'hardcoded' = lasso_uniqueid,
-expires = 'Mon, 26 Jan 2015 10:46:18 GMT',
-path = '/'
)
will result in this sent to the browser:
Set-Cookie hardcoded=414F2A7D-F4DE-4111-9E8C-A3D3DC9E1106;expires=Mon, 12-Jan-2015 10:53:12 GMT;path=/
Comments
It is related to fix #7933
'hardcoded' = lasso_uniqueid,
-expires = date('26 Jan 2016 10:46:18 GMT'),
-path = '/'
)
returns:
`Set-Cookie hardcoded=C13CBCAC-69E0-4930-AB3D-31B28A198805;expires=Tue, 26-Jan-2016 10:46:18 GMT;path=/`
This'll be made clearer in the next docs update.