Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=PNaduGKrWttPM1TswaH2oeNDInbz83p1tvGYxYIKjKbZnYBmztMEb2vvoSAEZITenwrFn0RYaURZsmJJfgeBnwD9TIO5XAo2RKD7f1B2okFMByXbaZWY8+yWXva87U+n9IHBLBor7i4sDQnnWOEHTqb354TpgB8Vixn+s5chaAg=
  ;
Message-ID: <20061204023057.28031.qmail@web56413.mail.re3.yahoo.com>
Date: Sun, 3 Dec 2006 18:30:57 -0800 (PST)
From: Rashmi Rubdi <dev_subscriptions@yahoo.com>
Subject: Re: Web spiders - disabling jsessionid
To: Tomcat Users List <users@tomcat.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ascii
Content-Transfer-Encoding: quoted-printable

One thing about search engine bots though is that repairs to jsessionid (re=
moving jsession id) from URLs won't be instantaneous, because they cache al=
l URLs, and on subsequent visits they visit each cached URL.=0A=0AThis mean=
s that even if you solve the problem of jsessionid now, you will still see =
some URLs jsessionid in your logs for a few months before they vanish from =
the crawler's cache. This is how it works for broken links as well, it take=
s a while for broken links to disappear from the crawler's cache.=0A=0AThat=
's why testing your case with your own crawler is better than waiting for t=
he next crawl from other search engines.=0A=0A=0A =0A______________________=
______________________________________________________________=0ADo you Yah=
oo!?=0AEveryone is raving about the all-new Yahoo! Mail beta.=0Ahttp://new.=
mail.yahoo.com

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org