06 December 2006 5:53 pm, Simon Pink wrote:
Hi there,
It is well noted by Google (and other search engines) that they do not like
session tracking info as part of the URL. This does include JSessionId, and
because Google visits your site as a cookieless user, every page indexed by
them
noted by Google (and other search engines) that they do not like
session tracking info as part of the URL. This does include JSessionId, and
because Google visits your site as a cookieless user, every page indexed by
them includes JSessionId, this is bad for numerous reasons - but the main
reason
Hi there,
It is well noted by Google (and other search engines) that they do not like
session tracking info as part of the URL. This does include JSessionId, and
because Google visits your site as a cookieless user, every page indexed by
them includes JSessionId, this is bad for numerous reasons
.
-Rashmi
- Original Message
From: Simon Pink [EMAIL PROTECTED]
To: Tomcat Mailing List (users@tomcat.apache.org) users@tomcat.apache.org
Sent: Wednesday, December 6, 2006 5:53:53 PM
Subject: JSessionId and Google
Hi there,
It is well noted by Google (and other search engines) that they do
in context:
http://www.nabble.com/JSessionId-and-Google-tf2297743.html#a7693602
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL
Simon wrote:
According to the Google Information for Webmasters page, it appears
that Google will not index/crawl pages correctly with the JSessionId
appended to the
You don't get it. They say, that your site should work correctly (i.e.
the navigation should work, the content should be
couldn't you simply create a HttpServletResponseWrapper object in a
filter, this object could overwrite the method that encodes the URL and
remove the JSESSIONID from it
Filip
Simon wrote:
Hi,
According to the Google Information for Webmasters page, it appears
that Google will not
Thanks, I could try this, but I was kind of hoping for a more general Tomcat
solution (if there is one). I know Resin has a 'enable-url-rewriting' flag
that you can set in it's config.
I guess the question still is, does anyone definitively know if jsessionid
does have negative impact on Google
