Why do some pages show the session id, and some don't?

[Guest]

My product pages don't display it in the address field, but in the categories or logging in, creating acct, etc. it does. Is this really needed? When I go to a page that doesn't show it, then go to another page that does again, it is the same # so it is saving it somewhere. This just seems to be an easy way to fix the googlebot problem where GB of data have been spidered for days... Or does the googlebot not work that way?

[Harald Ponce de Leon]

My product pages don't display it in the address field, but in the categories or logging in, creating acct, etc. it does.  Is this really needed?

 

On every first request made to the store, a session ID will be generated and is included in the page links. The first click on a store will ofcourse have the session ID in the url as it is part of the link - if your browser has cookies enabled, further clicks will no longer contain the session ID as it is being stored in a cookie.

 

Depending on your server setup, going from HTTP to HTTPS mode may be problematic for the cookie, which is why the session ID is appended in the url when going to HTTPS mode, or going to HTTP mode from HTTPS.

 

If the same domain is used for HTTP and HTTPS servers, and the same directory on the server is used to store the session files, there is no need to append the session ID in the url when going to and from HTTP and HTTPS mode.

 

However, if the domains are different or if the session directory is different, having the session ID in the url is required - and having mysql based sessions could be a further requirement in order for the customer to retain their session information.

[sneakyimp]

I have seen other open source projects (such as GALLERY at sourceforge.net) that use server configurations to hide the details in the URL...so that the URLs look really user friendly and stuff....am i thinking of the HTACCESS file??