QUOTE(Christian J @ Jan 14 2013, 05:53 PM)
QUOTE(joyful @ Jan 14 2013, 10:16 PM)
For some reason I find that the iframe gets the cookies of the 3rd party site (the site that is using the app), not the domain that it is on (the framed page). I don't understand why this is.
That sounds strange. If you're correct it's a security hole in the browser.
Can you show us some sample code illustrating this (preferably a minimal test script)?
Hey Christian and Pandy,
Sorry that I dropped this topic for awhile, I have been really busy over the past few weeks.
I believe the issue I am encountering is not due to the cookies in the iframe, but, instead, it is due to the fact that the framed webpage is on a different domain than the main website.
The reason I have the framed content on a different domain, is that I want the framed webpage to be ssl (https). I have a website, lets say mysite.com, which is not https. However, my host offers a free ssl connection to my root directory. So, I can access the content of mysite.com via https by go going to something like:
https://myusername.myhost.com/mysite/So basically, I have
http://mywebsite.com (not https) where users can login, edit things, etc. Then, anywhere that my plugin is on the web, users view my framed webpage which is at:
https://myusername.myhost.com/mysite/Obviously, both of these domains are on the same server. Is there some way I can allow cookies set on the main http domain, to be accessed via the https host subdomain, and vice versa?
Thanks a lot!
--Joyful