View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003241||OXID eShop (all versions)||4.09. SEO, SEO URL||public||2011-09-13 10:16||2012-12-10 13:34|
|Product Version||4.5.2 revision 38481|
|Target Version||Fixed in Version||4.5.3 revision 39087|
|Summary||0003241: robot detection quite imprecise|
|Description||the list of keywords that are used to detect robots is |
Several of the most common bots stay undetected with this list, for example msnbot, bingbot or yandex.
Additionally you have the entries robot and splider twice in that list.
|Tags||No tags attached.|
||We will add bots to our list, but they will have influence when parameter blForceSessionStart is seted to true.|
||what do you mean? what kind of influence? why is the list of knows robots affecting session start?|
actually we plan to remove search engine (SE) check at all, because:
- new SE bots appears and we cant always be up-to-date (latest bot list containts > 300 items..);
- major SE does not like if we deliver different content for different user agents;
- many links which should not be accessed by SE allready has rel="nofollow" attribute.
so for current phase i will append existing list with few most popular bots
now session is only started on special actions + if user agent is not in robot list. exeptionally session automatically is started in special case if config parameter "blForceSessionStart" is TRUE.
in next major release we plan to refactor session handling so, that session is started only when some session data is set, not on some specific cases like it is now