Guest Posted March 3, 2004 Posted March 3, 2004 Hi Everybody - I've got an odd problem. When a user first comes to the front page of my store, all links on that page include what looks like a session ID, but are otherwise properly formatted. For example, a link that should be http://address.goes.here/index2.php?cPath=23 is instead http://address.goes.here/index2.php?osCsid...umbers?cPath=23. Clicking on that link just causes the landing page to reload (probably the args aren't getting parsed correctly since they're separated with a ? instead of a &), but on the freshly loaded page, the links are normal (no osCsid). Any ideas why this might be happening? Thanks in advance! Aaron
user99999999 Posted March 3, 2004 Posted March 3, 2004 Hi, I agree Something is not quite right in the session/cookie logic there. Basically if you didnt send a cookie, or if you send a expired cookie then you will get a session ID in the URL. I think kill sids on http url's and a guest that doesnt accept cookies cant add anything to the cart. A logged in customer that doesnt accept cookies can get session id on the url. So I think it just a matter of diggin in and find that PHP3 logic and change it to compatible PHP4 trans_sid compatable. Dave...
fmerrill Posted March 3, 2004 Posted March 3, 2004 The sessionID should be there on the initial landing page, as the cookie that may have been written hasn't yet been read from the users machine. Once a link is selected, it will get read and then no more session IDs. If cookies are forced, the session id shouldn't ever show. The problem in your example looks like you maybe have made a mod that is adding the sessionID or some other random numbers before the actual category path is identified. I assume the same thing appears for products by these numbers splitting the product_infp.php and product_id portions of those urls? Is this just happening in the Categoires box? Is it happeneing on every link as you said like in the infoboxes? Are you sure that it is a sessionID? I'm not sure what exactly is up there without seeing it, but it is intriguing!
user99999999 Posted March 3, 2004 Posted March 3, 2004 What im sayin is exposing the session id in the URL is not acceptable. Giving the session ID in the url on 'first landing' is wrong and needs to be fixed. I hope HPDL can understand this" Treat all page request as 'CUSTOMERS' that accept cookies and then weed out the spider and etc. Dave...
Guest Posted March 4, 2004 Posted March 4, 2004 Thanks to everyone for their help - turning Force Cookies on did away with the problem. Now we'll see if I get a lot of ranting e-mails demanding that we stop forcing the use of cookies! Thanks again for the help. Aaron
Recommended Posts
Archived
This topic is now archived and is closed to further replies.