Gang,
Thanks for the input.
I've done a couple of things to fix this, including the suggestions of:
* Including the id/token in the URL
* using <CFLOCK> around any session vars
* Setting the "locking" stuff in the CF Administrator
To keep my CFLOCK usage to a minimum, at the top of any page, I'm coping
"Session" into another local structure, and use it to do my reads.
So far, nothing is breaking, but I don't know 100% if it's fixing the issue
until we do some testing with folks inside the client's network (which we're
doing in a few minutes).
FYI, the issues only happen INSIDE the company's LAN - the CF server and the
client machines are all basically one hop away from each other. No proxies
are involved. The issues do NOT happen with us OUTSIDE the lan, going
through the firewall. I still suspect there's something funky going on
inside their LAN - perhaps their client machines are set to munge cookies,
or there's some weird communication issue going on internally. But I'm
hoping that all this will be moot - I'm personally betting on the "passing
the id/token" fix being the key thing here, i.e. short-circuiting the
necessity of a cookie in the first place.
--Scott
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
