2011/6/28 Mark Thomas
>
> On 27/06/2011 21:42, Martin Kouba wrote:
> > You may inspire yourself with code from my blog post -
> > http://www.symbiont-it.cz/crawlersessionmanagervalve-a-tomcat6, lines 86
> > to 134 (text is unfortunately in czech :-).
>
> No problem,
You may inspire yourself with code from my blog post -
http://www.symbiont-it.cz/crawlersessionmanagervalve-a-tomcat6, lines 86
to 134 (text is unfortunately in czech :-).
Cheers,
Martin
Dne 27.6.2011 15:29, Mark Thomas napsal(a):
On 27/06/2011 14:19, Martin Kouba wrote:
Recently I've
ke
CrawlerSessionManagerValve implementor of
org.apache.catalina.SessionListener and remove expired session info on
SESSION_DESTROYED_EVENT. I tried to modify the code and it seems that
CrawlerSessionManagerValve works now even better.
Martin Kouba
--
Recently I've been using adapted code of CrawlerSessionManagerValve from
Tomcat 7 on Tomcat 6 (JBossWeb 2.1.4 respectively). It works well.
However I observed a lot of HTTP sessions that were created even if
CrawlerSessionManagerValve logged sucessfull bot detection. Finally I
found that proble
What is the reason NOT to assume that request with more than one
User-Agent header originates from a bot?
See lines 133, 134 in Tomcat 7.0.14.
Thanks
Martin
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For addi
