Hi!
I run a tomcat-based portal (Liferay) and we did nice work with it. When
it came to google, we realized we are punished for using tomcat, since
there seems to be no way in disabling jsessionid (session id appended to
URL). Google act as a non cookie browser and hence he is served with non
From: Marian Simpetru [mailto:marian.simpe...@esolutions.ro]
Subject: JSESSIONID and impact on google
When it came to google, we realized we are punished for using tomcat,
since there seems to be no way in disabling jsessionid (session id
appended to URL).
Of course there is - don't
On 09/02/2010 14:31, Marian Simpetru wrote:
Question is: Is there a way to configure tomcat to only use cookies (not
append jsessionid to URL for cookie0less browsers). I've been told Jetty
or resin is configurable in this aspect.
There will be in Tomcat 7 onwards. Prior to that, using
Thank you,
I guess session is created since a user could change preferred
language.. In a portal is basic stuff. Then you need session since page
one. We write JSR168 portlets on top of the Liferay portal ..
It's really an useful feature.
Thanks for your time, we look forward for tomcat 7 I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marian,
On 2/9/2010 9:31 AM, Marian Simpetru wrote:
Google act as a non cookie browser and hence he is served with non
unique URLs (because of session ID is appended to URL).
I heard at one point that Google's crawler *did* support cookies. I
On 09/02/2010 15:46, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marian,
On 2/9/2010 9:31 AM, Marian Simpetru wrote:
Google act as a non cookie browser and hence he is served with non
unique URLs (because of session ID is appended to URL).
I heard at one point
On 09/02/2010 16:32, Marian Simpetru wrote:
jsessionid in URLs returned around 79 million search results.
Yep. I know they're there.
google search on jsessionid SEO will give you lots of examples.
On a question asked to google, they reply by explaining the algorithm
(multiple URL with same
If you want to be seo friendly then change the application so that
session is not in the url.
Google sees each unique url as one page. With each visit to a jsession
site it will see the same content on multiple pages and the score will
go down for those seo terms.
Simple answer: Use cookies for
