I am using iPage.com host. To be able to use PHP periods within their host I have to add session_save_path('/home/customers/web/.../cgi-bin/tmp') at the beginning of each page (during my situation only index.php because everything goes trough index.php first).

Now, they instantly add the session id towards the finish of each and every URL asked for such as this: website.com/movies/particulars/?PHPSESSID=4s54kjhdl...

I believe this really is leading to problems and may affect google indexing and Search engine optimization..

Preventing this?

Your "host" is not leading to the problem, PHP is appending this data. Particularly, PHP is set up to append the PHPSESSID variable towards the Hyperlink to allow PHP to trace the session. You can alter the relevant setting using ini_set just before calling session_start, or even more permanently by upgrading the php.ini file (though since you are located this latter is most likely out). This really is a listing from the available runtime configurations for periods in PHP.

As you can control set up value is appended towards the finish of the Web addresses, it's needed to trace the periods. Alternatively you are able to configure PHP to make use of snacks to trace periods, but needing snacks to trace periods may break the application for customers who reject snacks.

In a nutshell, you are able to control the session ID to really make it just a little more attractive (by renaming PHPSESSID to something more amenable or making the worthiness less cryptic) but unless of course you need to use snacks to keep the session, you are tied to this "garbage" in your URL. Should you only use snacks some customers might not have the ability to keep up with the session.

Make it possible for cookie based session handling you are able to execute either:

// stop PHP from instantly embedding PHPSESSID on local Web addresses

ini_set('session.use_trans_sid', false)


// just use snacks (no url based periods)

ini_set('session.use_only_cookies', true)

If you cannot modify php.ini yourself, that you can do the next:


This makes PHP to make use of cookie based session handling, and never append the session id towards the URL (which might be a security risk anyway).

Either configure it to make use of cookie-based periods or turn of periods entirely.