Hi Sarah,
here's another thing to try if Elliot's idea doesn't help. It might not be the
fix but could you place this in each Application.cfm and see if it helps?
<!--- set session coookies --->
<CFIF StructKeyExists(cookie,"cfid") and
StructKeyExists(cookie,"cftoken")>
<CFCOOKIE name="cfid" value="#cookie.cfid#">
<CFCOOKIE name="cftoken" value="#cookie.cftoken#">
</CFIF>
for my mind, I can only think of two things that would cause this - caching (al
la what Elliot said)and a mix-up with the session "cookies" passed between
browser and webserver.
CGI.HTTP_COOKIE=CFID=12486; CFTOKEN=52055531; JSESSIONID=e6305879eada$5F$0F$C
>> The 'hold' seems to last for 20 minutes which argues something to do with
>> the CF server variable timeout
possibly more the session variables (since they're dying after 20 min)
now, both apps have their own Application.cfm, yes? (things get a bit messy
with cascading/including Application.cfm's).
I'd do a trace on the CGI.HTTP_COOKIE values as you move from app to app - see
if they change. In theory, once you login into "studentportal", the
CGI.HTTP_COOKIE values should change. If you go back to "qmis", those values
will probably still be there (not been over written) but they should be
ignored/invalid for any session within that application on the server. A quick
login OR the code above should sort that.
give it a go and let us know?
HTH
cheers
barry.b
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sarah Barry
Sent: Saturday, 9 April 2005 12:34 PM
To: CFAussie Mailing List
Subject: [cfaussie] server caching page
Have checked the cfaussie list for a similar problem and Tom's latest problem
seemed to be an echo but that solution did not work!
We need to split our web into a php site and 2 cold fusion sites.
The cold fusion sites work happily at the moment from
www.qantmcollege.edu.au/studentportal and www.qantmcollege.edu.au/qmis
We wanted to set up subdomains respectively at
http://studentportal.qantmcollege.edu.au and http://qmis.qantmcollege.edu.au.
Both sites start with index.cfm.
the portal has an application.cfm and uses /cflogin
Qmis had no application file until I started to use one to try and solve the
problem and does not use cflogin at all.
The issue is that whichever site you go to first holds that index.cfm as the
one to deliver when you swap to the other site. it does not matter which order
you do it in nor what activity takes place on the sites. It is only the
index.cfm file that gets hooked - other files within each site deliver okay.
The DNS resolution is okay because hans.htm displays as the right file for each
server.
Whatever mess the subdomains get into, the original subfolders continue to work
as they were designed and deliver the right files.
The 'hold' seems to last for 20 minutes which argues something to do with the
CF server variable timeout. The Cf server has its own variables (not J2EE) and
ap is 2 days; session 20 mins. The web server is IIS (have not checked what
version) and its timeout is 900 secs for the keep alive.
The problem is not session based. That is once the index file is corrupted for
one user on one machine it remains corrupted for all users until the time out.
So it looks like a web server problem.
I saw a fullasagoog article saying that caching happened when the cfapplication
had loginstorage set to session there were caching issues but the default for
this attribute is cookie anyway and setting that did not solve anything.
There is no proxy caching in operation on the network.
Any ideas?
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia
Developers: http://lists.daemon.com.au/
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
