Welcome, Guest. Please Login or Register.
July 14, 2025, 09:46:05 PM
Home Help Search Log in Register
News: SMF is the next generation in forum software, almost completely re-written from the ground up, make sure you don't fall for cheap imitations that suffer from feature bloat!

YaBB SE Community  |  English User Help  |  English Help  |  Using Yabbse in a frame on separate domain « previous next »
Pages: [1] Reply Ignore Print
Author Topic: Using Yabbse in a frame on separate domain  (Read 369 times)
eteune
Jr. Member
**
Posts: 64


Estoy un tlacuache!

WWW
Using Yabbse in a frame on separate domain
« on: May 16, 2003, 02:27:24 PM »
Reply with quote

I have YaBBSE running at one domain:
www.domain1.com/directory1/index.php
and I am trying to use it inside a frame at another domain:
www.domain2.com/frame.htm
I can login, but then if I try to navigate to anything it sends me back to the login screen.

Now, I can use it in a frame in domain1,
www.domain1.com/directory2/frame.htm
and everything works fine.

Why does it work in one frame but not the other domain's frame, and can I make it work in the other domain's frame?

thanks,

Ed
« Last Edit: May 16, 2003, 02:27:38 PM by eteune » Logged

...sin otra luz ni guía
sino la que en el corazón ardía.
(San Juan de la Cruz)
Michele
Beta Tester
YaBB God
*****
Posts: 584


I can't wait for YaBB SE 2!

Mad+Moya WWW
Re:Using Yabbse in a frame on separate domain
« Reply #1 on: May 16, 2003, 03:16:13 PM »
Reply with quote

Browsers are specifically designed not to share cookie info between domain names. That prevents one site from "stealing" another site's cookie info.

HTH, Michele
Logged

formerly Mad Moya
PfaBB - http://pfabb.lunabyte.com
Daniel Hofverberg
YaBB God
*****
Posts: 582


WWW
Re:Using Yabbse in a frame on separate domain
« Reply #2 on: May 16, 2003, 03:43:44 PM »
Reply with quote

Not all browsers, I might add (No browsers allow cookies to actually be stored across domains, but only some have problems with use of forums in frames in a different domain than the actual frameset) - That is because some browsers consider that third-party cookies, such as IE 6.0.

You can generally make it work by lowering the security settings in the browser, but that would then have to be made for each user...
Logged
Michele
Beta Tester
YaBB God
*****
Posts: 584


I can't wait for YaBB SE 2!

Mad+Moya WWW
Re:Using Yabbse in a frame on separate domain
« Reply #3 on: May 16, 2003, 04:06:11 PM »
Reply with quote

You can make frames work, but you will never (should never) get cookies to work across domains.

Any browser that allows one domain to read the cookie from another domain would be one BIG security hole in that browser. Note I'm not talking sub-domain to domain, but top-level domain to top-level domain. If you ever getting it working in a browser, it's time to dump that browser. :)

Michele
Logged

formerly Mad Moya
PfaBB - http://pfabb.lunabyte.com
eteune
Jr. Member
**
Posts: 64


Estoy un tlacuache!

WWW
Re:Using Yabbse in a frame on separate domain
« Reply #4 on: May 16, 2003, 04:30:47 PM »
Reply with quote

Doh!, domains and cookies, forgot about that.
thanks, will have to find a new host then to put everything on the same domain or just navigate to a frame on the second domain, or make it match the look of the first domain.
Logged

...sin otra luz ni guía
sino la que en el corazón ardía.
(San Juan de la Cruz)
[Unknown]
Global Moderator
YaBB God
*****
Posts: 7830


ICQ - 179721867unknownbrackets@hotmail.com WWW
Re:Using Yabbse in a frame on separate domain
« Reply #5 on: May 16, 2003, 04:58:48 PM »
Reply with quote

If it's a *subdomain*, you can use my Global Cookies mod.  Otherwise, it can't be done.

-[Unknown]
Logged
Pages: [1] Reply Ignore Print 
YaBB SE Community  |  English User Help  |  English Help  |  Using Yabbse in a frame on separate domain « previous - next »
 


Powered by MySQL Powered by PHP YaBB SE Community | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.
SMF 2.1.4 © 2023, Simple Machines
Valid XHTML 1.0! Valid CSS

Page created in 0.099 seconds with 21 queries.