Is this capability somewhere else, perhaps not needed anymore, or perhaps still
on the backlog to be ported up to TC7?
Holy smokes that was a quick response! Thanks!!!
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Thursday, February 24, 2011 5:47 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 missing Tomcat 6's Context disableURLRewriting Setting?
On 24/02/2011 22:44, Scott
Looks like the TldConfig class changed significantly between these versions
such that now TLDs that are under WEB-INF/classes (e.g.
WEB-INF/classes/META-INF) are no longer scanned/processed.
This is an issue for us in development as some of our MyEclipse projects are
TLD library projects that
Location
Problem
On 23/02/2011 19:13, Scott Hamilton wrote:
Looks like the TldConfig class changed significantly between these versions
such that now TLDs that are under WEB-INF/classes (e.g.
WEB-INF/classes/META-INF) are no longer scanned/processed.
This is an issue for us in development
You've got two connectors in that server.xml, and one of them is AJP
without any real other configuration parameters. If memory serves the
thread limit when not specified for a connector is 200...
Can we assume you're using apache as a web server connecting to tomcat?
What are you using there -
Awesome dude (that you submitted the patch so quick - I've not looked at
it in detail yet). Thanks!
-Original Message-
From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
Sent: Monday, August 23, 2010 2:33 PM
To: Tomcat Users List
Subject: Re: Is there a better way to disable
Can you also include the dump of the thread that is holding the lock? In other
words, what's the other half of the deadlock?
-Original Message-
From: Milo Meerkat [mailto:milo.meer...@gmx.com]
Sent: Monday, August 23, 2010 10:53 AM
To: users@tomcat.apache.org
Subject: Tomcat 6.0.29 -
Sorry to pull the thread back to my original problem, but I have one
more question here.
So far it looks like there's no way to prevent JSESSIONIDs from being
injected into URLs that Tomcat might encode unless you implement a
servlet filter to override that behavior.
My follow-up question is
Using Tomcat 6.0.29, but I think this is version-independent (correct me
if I'm wrong), at least for the 6.0.x versions.
From what I understand (see
http://randomcoder.com/articles/jsessionid-considered-harmful for
instance - I also scanned various aspects of the tomcat source code)
there is
.
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Tuesday, August 17, 2010 6:16 PM
To: Tomcat Users List
Subject: RE: Is there a better way to disable JSESSIONID in the URLs?
From: Scott Hamilton [mailto:scott.hamil...@plateau.com]
Subject
10 matches
Mail list logo
