Using IP in setcookie()

jburns131

This is my situation:

My company has changed the name of the company I work for, and we have a new domain. I am creating a login system for our new website using cookies.

Right now we have the new domain aliased (I think that's correct). So we have both domains pointed to the same directory structure. But if I go to the new domain and login, when it goes to the next page (which checks for the correct cookie), it uses the old domain. This is reaking havoc testing things.

I've tried to use the IP rather than domain name while creating cookies, but that doesn't seem to work. Is there a way to do this?

The only solution I can see is to create 2 cookies, one for the old domain and one for the new domain, and change my testing to accept either one. But we plan on releasing the new site on Jan 1st and disabling the old domain. When that happens, I have 2 options, either leave the code as it is, or go through all my code and remove any reference to the old domain and the cookies that were create for it. (I'd have to do this while the site is live)

That seems sloppy to me, so any advice would be great. I'm trying to keep the transition as smooth as possible, as this is an established company with a large client base.

superwormy

Well first off, your code probably shouldn't be setting cookies in more than a few places, so I don't see that as being a big deal.

Are you explicitly setting the domain name in the cookie? Why can't you just set it based on whether you're on the old domain or the new domain? That way, if you're on the old domain, you login under old domain, and checks get done against old domain, and if youre on the new domain, cookies gets set under new domain, and checks get set under new domain...

jburns131

I only set cookies once, when they login. But you have to set the domain for the cookies.

And this is how it happens:

Old Domain: www.myoldsite.com
New Domain: www.mynewsite.com

OK, someone goes to www.mynewsite.com/login.php and enters a username. When they click 'Login', the script goes to 'client_access.php' and makes sure it's a valid login and sets the cookies. I then use a 'header("Location: welcome.php");' if everything is ok.

The problem is that because of the aliase/redirect, the user will login on 'www.mynewsite.com/login.php', yet along the line it goes to 'www.myoldsite.com/welcome'.

The welcome.php tests to make sure that the user has the correct cookie, and if not the user is redirected to 'login.php' with an error message, yet it won't have the correct cookie because it's a different domain then what's in the cookie.

So my main problem at the moment is the aliase/rederect. I'm not in contact with the web hosting company, the person in charge of this project is, but all I know is that they got a new domain, and now the old and new domains point to the same directory structure. I'm not sure what is causing it to switch between domains since I'm only using relative links in my script.

But that brings me back to the whole problem. Both domains point to the same IP, so is there a way to set a cookie to an IP address rather than a text domain?

Did I make sense?