At a guess, I would say that the problem is that some browsers prevent
cross-domain cookies.  That is, if the title in the URL bar is at
www.domain-a.com, and the content is from www.domain-b.com, the cookies
are blocked.  Now, this may only pertain to things like embedded data
(webbugs and ads) but it may also affect frames.

That's all I can think of offhand.

--benD

William H Bowen wrote:

> All,
>
> I am being forced by an organization higher up the food chain to now
> only grant access to certain parts of our corporate external site via
> frameset.
>
> It's a domain name thing, they don't want us using ours anymore
> (www.esca.com) despite years of brand recognition in our industry.
>
> So here's the issue. many of the parts of the site they want accessed
> through the frameset are password protected and access is granted by
> reading a cookie value set from my site.
>
> Now, I did a bit of research because of the obvious third party cookie
> issues caused by frames, and I found that session management is
> "compatible" with frames (sort of). I set up a test and found that if I
> access it directly (www.esca.com/blah url ) everything works fine
> session variable initiate and expire as requested, but if I access it
> via frames, the login doesn't work.
>
> What am I missing? Does the session have to be init'ed on the outside
> frame? If so can I init the session with _javascript_ and then write to it
> with CF? I don't have control of the outside frame, it's hosted in
> England, but if I need to I can probably get something added there.
>
> The external frame is being handled in the OpenMarket CMS and my site is
> all CFMX.
>
> Please help!
>
> --
>
> will
>
> ----
>
> William H Bowen
> Marketing Communications Manager
> ALSTOM EAI Corporation
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to