Use same vB on different Domains (cookies)

I haven't tested it in all circumstances but in only the way i needed. This may not be the best method but I think its the only one that works as of right now.

Tested Domain Situations:
-------------------------------
1site.com
2site.com ( which the real url is 1site.com/2site/ )
-------------------------------

Open Functions.php and find

PHP Code:

{ // try unsetting without the / at the end 


before each setcookie function ( should be 3 within about 25 lines or so ) add

PHP Code:

setcookie($name, $value, $expire, "your-path", "your-domain", $secure); 


this should write the cookies for each domain you set it for and allow people to view each one and not have to log in. Please give me feed back on this for i would love to see my first vb hack work

[Mephisteus]

Isn't this a default feature through the Settings part of admincp? Just wondering...

[AlexanderT]

Often a site is accessible through various aliases. So for instance you could access the same site with

namea.com
namea.net
nameb.com
nameb.net

That would be 4 different domain names, but only one copy of vB on one server - so perfectly legal. If the hack works as advertised, it is a nice addition.

[Paris Holley]

yes it works just like that, I just have to make it so that it logs out too....

[noox]

I'm pretty sure that this will only work in your situation with subdomains or paths.

You cannot set (or read) a cookie for a foreign domain. This would be a big security problem.

So you only may set a cooky for the same domain and same path. Additionally for parent directories or the "root" domain. So it is possible to set a cookie from www.domain.com for domain.com which can be read from domain.com.

The IE has a small glitch if you do not set the cookie domain: If you then set a cookie to domain.com you cannot override it from www.domain.com. Let's assume a simple auto-login script. Somebody logs in using domain.com. Later he comes back using www.domain.com. He is automatically logged in but cannot logout as long as he tries it on the domain www.domain.com! So setting the cookie domain is generally a good practice.

If you realy want to set a cookie for another domain there are some possibilities. You could insert an image or an iframe within your page where you transfer the information via query string. This image or page in the iframe is located on the other domain and sets the cookie.

Because of security issues the newer browsers standard security settings prohibit setting cookies this way on domains not equal to the main site or the main frameset. This is for instance a problem for the banner ad agencies.

So my only idea is to forward to the a script on the second domain which sets the cookie. This script forwards back to the initial script. I havn't tried that yet, but it should work.

[noox]

I've found another solution which should work in some situations:
Use the IP as cookie domain. This will only work if all domains you want to have access are using the same IP. This is the case if you have additional domains pointing to the same webhosting account.

Attention: Do not use this if foreign websites also use the same IP. (As on most shared hosts.) This would introduce a big security hole!

[Floris]

Originally Posted by noox

I've found another solution which should work in some situations:
Use the IP as cookie domain. This will only work if all domains you want to have access are using the same IP. This is the case if you have additional domains pointing to the same webhosting account.

Attention: Do not use this if foreign websites also use the same IP. (As on most shared hosts.) This would introduce a big security hole!

More info?

[Zach]

Originally Posted by Velocd

From vBulletin.com:



I'm uncertain, but your suggested use of this hack may violate that rule (in bold).

I have hundreds of domain names, I park them on my forums.

Just because you can get to it by two or three hundred different domain names doesnt mean that its a different forum.

Otherwise I would be one broke mofo


(I also 301 - doesnt stop search engines from listing them more than once, or get them to pull listings anytime soon after I make a change and forget to 301 right away - I only 301 certain forum pages, since I use things like global.html (.php) in hundreds of different places on many different domain names that I do not want 301ed to the wrong place)

[Zach]

Originally Posted by noox

I've found another solution which should work in some situations:
Use the IP as cookie domain. This will only work if all domains you want to have access are using the same IP. This is the case if you have additional domains pointing to the same webhosting account.

Attention: Do not use this if foreign websites also use the same IP. (As on most shared hosts.) This would introduce a big security hole!

I think I love you.

[peterska2]

I'm gonna watch this as I have trouble with cookies on my forums since I went to dual domain names.

[geezzaa]

Let me get this right, im dislexic so its got me a bit confused
I have 1 site that i want to have just a normal https for my visitors and i want to add a https connection
Does this mean i can http://www.ukcultivator.biz and https//:www.ukcultivator.net and run them to the same site
Will this still mean i can have both http and https connections on the same forum

Thanks in advance