Keep your URL as www.domain.com, and prevent domain.com

NeXEA

Hello.
Not sure if this is understandable but I remember I saw a code out somewhere that did this.
All your visitors would always be under www.domain.com and if they put in domain.com they would be redirected to www.domain.com.

I am wondering this because my site uses directory specific cookies, and if my visitors are at domain.com instead of www.domain.com it freaks and says they have to log back in. I know that Demonoid has kinda what im looking for, and some others I can't think of right now.

I know that you can do this with .htaccess in Apache, but Im running Lighttpd and haven't a clue where I could start.

If this is completely confusing, I'll try to re-describe it.

Help is greatly appreciated.

dagon

RewriteCond %{HTTP_HOST} ^domain.com [NC]
RewriteRule ^(.*)$ http://www.domain.com/$1 [L,R=301]

NeXEA

So how do I do this with Lighttpd. Do i put it in the config file or where does it go.

dagon

NeXEA;10903703 wrote:
So how do I do this with Lighttpd. Do i put it in the config file or where does it go.

Never used Lighttpd, read their docs

bradgrafelman

Better yet:

NeXEA wrote:
I am wondering this because my site uses directory specific cookies

Unless you have multiple subdomains, one possible solution would be to set the domain attribute of your cookies to ".yourdomain.com" - this would cause the cookie to work across all subdomains (including the null subdomain).

NeXEA

Ok. So if I under stand you, then if I change my domain for the cookie to .domain.com It will work.

This is how I go about this

function logincookie($id, $passhash, $expires = "0x7fffffff")
{
	setcookie("id", $id, $expires, "/");
}

So if I change the domain to this:

function logincookie($id, $passhash, $expires = "0x7fffffff")
{
	setcookie("id", $id, $expires, ".domain.com/");
}

It should work. Right??

bradgrafelman

Not quite; see the manual for the order of parameters (path and domain are two separate parameters): [man]setcookie/man.

Also... I've never seen the 'expires' parameter defined by a string containing what looks like a hexadecimal number; are you sure that's correct? The manual suggests that setcookie() only takes a Unix timestamp.

NeXEA

After looking back over I finally got it.
And for why the time was hexadecimal, I couldn't tell you.
It was like that. I copied it from one of the scripts I used. It might have been because the script was made back when PHP4 was around, or what. I did a google search and it came back with the date of
03:14:07 UTC on Tuesday, 19 January 2038.
So whatever. I got it fixed.
@ Thanks for pointing me back to the PHP functions page.

NeXEA

Just wondering. How do I unset the coookies
I have a function that looks like this

function logoutcookie() {
setcookie ("id", "", time() - 3600); 
}

And it should work right. Or do I need to unset the domain and path too.

bradgrafelman

You'll need to use the exact same parameters as you did to set the original cookie, yes.

EDIT: That excludes, of course, the expire and value parameters, since those are the values you're trying to alter.