>Hi,
>As you may know url rewriting feature is not a nice thing when spiders
>come to index your site -
>http://gabrito.com/post/javas-seo-blunder-jsessionid.
I'm having such trouble with JSESSIONID and search engines Google,
Accoona, Alexa and Exalead.
My approach was to contact each firm, and a
I've searched and searched for a way to get rid of the sessionid in my
URL's from tomcat/struts. What happens is that Google and other search
engines think that each new session is a unique version of the page,
frustrating their own caching.
I added <%@ page session="false" %> to the top of each
We have a Tomcat application, which binds to port 8080 and AJP 6135. At
3 am we restart this application (because of a memory leak). But
sometimes it is unable to bind to it's own port, and it just dies and
never starts. Naturally this causes unhappiness. The server.xml is:
And the
i.apache.org/tomcat/HowTo#head-45c3314139cb900ddd43dde2ff671532e6e844bc
-Bryce Nesbitt
http://www.obviously.com/
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe,