If the various cfapplication tags have different names, timeouts, or
other different attributes, then that could be the source of the
session problems you are seeing. Perhaps the person using MSIE 7 is
the only person that visits a certain maintenance page that is
influenced by a different
PS - There are multiple a few cfapplication tags in our system. However, it
uses FuseBox 3 and my understanding was that this could be done in
sub-folders / circuits without confusion. For instance, we use the CFFM
file manager with CKEditor in the cms and that has an application.cfm file
with
Mike,
To answer your question, it seems to be tied to a particular browser (IE 7
or 8) on a particular computer (ie IE 7, 8 work for most users).
Also, re: session variables, looking in CF Admin, it looks like we have Use
J2EE Session Variables as well as Enable Application Variables and
Enable
of cache) to see if that helps.
Again, I appreciate the thoughts and suggestions.
Nick
-Original Message-
From: Mike Chabot [mailto:mcha...@gmail.com]
Sent: Thursday, December 15, 2011 5:16 PM
To: cf-talk
Subject: Re: One app kills another's session
Sometimes switching to J2EE
Maybe see if you are up to date with CF patches.
I would put in a lot of logging code to track the session tokens, as
well as other session and cookie variables, and try to isolate exactly
where the problem occurs.
-Mike Chabot
On Thu, Dec 15, 2011 at 8:30 PM, Bryan Stevenson
-talk
Subject: Re: One app kills another's session
Sometimes switching to J2EE sessions fixes odd session issues. If you
are able to do this it might fix the problem. J2EE sessions work
well.Try doing a site-wide search for the cfapplication tag to make
sure there is only one in each site
Hey All,
Can't say that I've bumped into this before.
1) 2 apps are involved and both use SESSION vars to store user details
once they login.
2) Both apps are set to setClientCookies in CFAPPLICATION
3) App 1 uses a standard login form where credentials are verified and
the SESSION vars
Bryan,
Are these apps running on the same domain or different domains, if
they are on the same domain then you will need to specify the path in
your session cookies so they don't invalidate each other (this
relatively new behavior due to the session fixation security hotfix
APSB11-04 released in
Thannks Pete,
Same domainyes.but you speak of a recent hotfixwell this is
CF 8 ;-)
Thankfully I have been told to shelve this issue for other major
priorities, but thanks for the tips...I may need to come back to this at
some point.
Cheers
On Thu, 2011-12-15 at 14:52 -0500, Pete
Several (most? all?) post-CF9 hot fixes apply to CF8 as well. :-)
On Thu, Dec 15, 2011 at 3:37 PM, Bryan Stevenson
br...@electricedgesystems.com wrote:
Thannks Pete,
Same domainyes.but you speak of a recent hotfixwell this is
CF 8 ;-)
Thankfully I have been told to shelve
:53 AM
To: cf-talk
Subject: Re: One app kills another's session
Bryan,
Are these apps running on the same domain or different domains, if they
are on the same domain then you will need to specify the path in your
session cookies so they don't invalidate each other (this relatively
new
about how that plays out
in CF apps would be greatly appreciated.
Thanks in advance,
Nick
-Original Message-
From: Pete Freitag [mailto:p...@foundeo.com]
Sent: Thursday, December 15, 2011 11:53 AM
To: cf-talk
Subject: Re: One app kills another's session
Bryan
Sometimes switching to J2EE sessions fixes odd session issues. If you
are able to do this it might fix the problem. J2EE sessions work
well.Try doing a site-wide search for the cfapplication tag to make
sure there is only one in each site. Sometimes there are multiple
cfapplication tags in a site
On Thu, 2011-12-15 at 20:16 -0500, Mike Chabot wrote:
Sometimes switching to J2EE sessions fixes odd session issues. If you
are able to do this it might fix the problem. J2EE sessions work
well.
Pretty sure they already are - but I can double checkthanks
Try doing a site-wide search
14 matches
Mail list logo
