Closed GoogleCodeExporter closed 9 years ago
Original comment by per.djurner@gmail.com
on 7 Mar 2009 at 9:26
It might also be a possibility to add the flash data obfuscated in the url? This
would seem a viable option.
Original comment by james.t....@gmail.com
on 4 May 2009 at 4:00
Yes, good idea!
Original comment by per.djurner@gmail.com
on 4 May 2009 at 6:49
one way to be able to store non-simple data (structs and arrays) in a cookie
would be
to convert it to json and then store it in the cookie.
Original comment by tpetru...@gmail.com
on 10 Jun 2009 at 12:00
When this is done we should remove this line from wheels/functions.cfm:
<cfset this.sessionManagement = true>
Then we check on application startup if session management is enabled and if
not we set
the default flash storage to be cookie based instead.
Original comment by per.djurner@gmail.com
on 13 Nov 2009 at 11:35
Setting to 1.0.1 since I want to get rid of that hardcoded
this.sessionManagement
setting sooner rather than later.
Original comment by per.djurner@gmail.com
on 13 Nov 2009 at 12:17
Original comment by per.djurner@gmail.com
on 16 Nov 2009 at 1:53
Original comment by per.djurner@gmail.com
on 16 Jun 2010 at 3:08
i would mark this off of the 1.1 milestone. more research is needed before
something like this is implemented.
Original comment by tpetru...@gmail.com
on 17 Jun 2010 at 5:47
Looking into it...
Original comment by per.djurner@gmail.com
on 20 Jun 2010 at 11:39
This is a horrible security risk but I can see the need if someone doesn't want
to use session management. Would it be possible to automatically choose to use
cookies if session management is disabled?
Original comment by andybellenie
on 21 Jun 2010 at 11:12
Original comment by per.djurner@gmail.com
on 21 Jun 2010 at 12:26
Yes, I'm working on this and that's the way I've implemented it. If session
management is enabled the default storage will be session, otherwise cookies.
Original comment by per.djurner@gmail.com
on 21 Jun 2010 at 12:32
Fixed in r4555.
Original comment by per.djurner@gmail.com
on 21 Jun 2010 at 6:30
Original issue reported on code.google.com by
per.djurner@gmail.com
on 30 Nov 2008 at 6:38