What is this thing in my site url ??

[the-wanted]

hi

when i type http://www.mysite.com then  the url changes to http://www.assyrian-home.com/?PHPSESSID=07a6d9de1bf4ea3e4170351956c5acb9;wwwRedirect .... what does that part of url mean ?

[Deaks]

this is the session code for your visit its different to everyone and it doesnt effect the runing of your foum.

[NanoSector]

the wwwRedirect means that the forum has added www. before the address. Doesn't affect the running of your forum either.

PS @ Runic: It's running and forum.

[the-wanted]

ya ok thnx and topic solved

[Arantor]

Just as a little more information for those curious about what's going on.

Firstly, PHPSESSID only gets added when cookies couldn't be saved to your computer. Bad search engines and odd settings in browsers will cause this, it isn't usually a problem, but if it's happening when you're normally logged in, it can be a sign of a mod breaking things it's not supposed to.

As for the wwwRedirect, that's because there is a different web address entered in the forum settings to what actually got to the forum, a redirect happens, but the wwwRedirect is added to ensure that there wasn't an infinite loop.

For example, if both domain.com and www.domain.com get to a forum, and the forum is set to use www.domain.com, typing in just domain.com will in most cases cause a redirect to www.domain.com with the wwwRedirect suffix to ensure everything's where it should be, but without redirect loops.

[Aleksi "Lex" Kilpinen]

Also, I've noticed that the wwwRedirect in itself seems to cause the session id to come up sometimes, so that if you go to a forum already using the www. prefix, it will not come up - but if you use just domain.tld and get redirected, it's more likely to appear.

[Arantor]

it's more likely to appear.

Typically that should be the case when subdomain independent cookies are not present, since you're doing a cross subdomain request which won't persist the cookie, and no cookie will at that point have been created so the session ID gets injected into the first request while there isn't a cookie - but it should go away shortly thereafter.

[Aleksi "Lex" Kilpinen]

Actually, that explains it - never thought of it much, but yes - I've noticed it's usually a one time thing, and the next page load won't do it anymore.

[Arantor]

Yup, because on the back of the first request, the cookie is now available again so the PHPSESSID shouldn't then reappear in the page, it's literally only when cookies are not available for whatever reason.

That's also why for a long time, search engines kept getting PHPSESSID pages, because they weren't receiving/sending cookies.