Dh!
Last night as I was about to fall asleep I realized I was off my rocker, but
in a different way.
Your problem with XPSP2 has nothing at all to do with ColdFusion, though the
appending may work.
The issue is related to not having two things: A properly formatted set of
P3P privacy
Hi,
I am retooling a large CF site and need to append the CFID and CFTOKEN to each
request as XPSP2 has locked out a lot of users who aren't allowing cookies.
There are too many pages to start digging through the links and forms to add
the URLTOKEN (unless I really need to). Is it not possible
I might be off my rocker - but are you implying that you are using cookie as
the Default Storage Mechanism for Client Sessions? Could I suggest instead that
you run all your client session requirements to a database instead?
I know that to create Search Engine Friendly URLs (
I'm sure you're rocker is fine.
I am using non-persistant session cookies for session management, not
persistant cookies.
A few members installed XPSP2 and it apparently disables all cookies,
persistant ant not, so that can login but the session cookie fails to be set,
and they get punted
I am using non-persistant session cookies for session management, not
persistant cookies.
Actually, in terms of the issue you are having, it wouldn't really matter. Even
if you use client variables in the database, Cold Fusion still uses the CFID
and CFTOKEN to identify the client. So they
5 matches
Mail list logo