I would like to know the answer too. Anyone here know what is the answer to your question. I'll do some research in Google and get back to you if I bump into an useful answer. You should email the people at iPage as they probably could give you an answer..
IN other words, this spider session ID killer works on the 'User Agent' of the visitor. The 'User Agent' of the first 2 simulators are not in in list of known spider 'User Agents', nad therefore, the session ID is not killed...
How did you determine the spider they were using?.
Would be nice to know..
Do we need to add these to the spider.txt file - or are they in-house bots ?
- is an in-house bot; my take on this issue though is that the SID killer should hide SIDs to all but known spiders, instead of working on the basis of downloading a (probably much larger) spider agent list. Or, even better, don't use SIDs at all!.
I do not fully understand sids(and there uses) - can we operate stores without them ? .
This post has been edited by.
: 08 March 2004, 13:20..
Yes, if you force customers to have 'cookies enabled' on their browser..
Currently I estimate the that about 65% of browsers have cookies enabled, but this number actually appears to be declining...
I have been testing my iPage site in three search engine spider simulators (SESS):.
The first two consistently refer to links with osc sessionn IDS. Not good..
The third, Webconf, shows my iPage site pages without sessionn IDS..
I have tinkered quite a bit to try and remove the references to session IDs by beefing up the spider list in spider.txt..
Does anyone know of a reliable search engine spider simulator that accurately shows what iPage site will look like to the most common spiders..
I have looked for documentation on the SESS's above but can't find anything discussing which spiders they are designed to mimic...
They mainly simulate what a spider can see not who the spider is..
A visitor from wiggum.w3.org (188.8.131.52).
This visitor used Lynx/2.8.4rel.1 libwww-FM/2.14..
A visitor from server146.ideal-dns.com (184.108.40.206).
This visitor used K2 www.summitmedia.co.uk..
A visitor from promo.directi.com (220.127.116.11).
This visitor used Googlebot...