web.xml and schema location

Back in Tomcat 5, we had the problem with tomcat trying to access java.sun.com. Lots of our servers are behind firewalls, so this caused an error in the log. We realized one way to fix this was just to remove the schemaLocation attribute from the web.xml files. Below is the top of the main

RE: web.xml and schema location

Message- From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] Sent: Wednesday, April 18, 2012 11:50 AM To: Tomcat Users List Subject: Re: web.xml and schema location 2012/4/18 Mark Claassen ma...@donnell.com: Back in Tomcat 5, we had the problem with tomcat trying to access java.sun.com

RE: how to populate userPrincipal in request object

I am not sure what your exact situation here is, but the user certificate stuff is only available if Tomcat requests it. And Tomcat only does this if Tomcat is using certificate based SSL authentication. I don't believe this will work if an Apache webserver is handling the SSL negotiation. Mark

Using log4J and getting rid of default logs in Tomcat 6

I would like to have all my logging go through log4J and not have the default XXX.date.log files created. Is there a way to do this? I got log4j working, as it says in the docs, but the localhost.date.log is still created and written to. From what I understand, I will need to put a

RE: Using log4J and getting rid of default logs in Tomcat 6

: [/host-manager] = like: log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost]=I NFO, MANAGER Thanks, Mark -Original Message- From: Mark Claassen [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 11:31 AM To: 'Tomcat Users List' Subject: Using log4J

RE: Using log4J and getting rid of default logs in Tomcat 6

Subject: Re: Using log4J and getting rid of default logs in Tomcat 6 See the note at the top of http://tomcat.apache.org/tomcat-6.0-doc/logging.html. By default, TC 6 only uses Juli for it's internal logging. Mark Claassen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] As it turns out

RE: Using log4J and getting rid of default logs in Tomcat 6

, June 12, 2007 10:47 PM To: users@tomcat.apache.org Subject: Re: Using log4J and getting rid of default logs in Tomcat 6 Mark Claassen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Thanks for the reply. I did get some logging to work already, so I am assuming that I have

RE: Reloading keystore - how to register a new TrusStore Manager for Tomcat?

Humm. I don't think this is how the certificate system is supposed to be used. The intention is that the truststore handles certificates authorities you trust. For an example, let's switch to the browser. Browsers generally trust Verisgn and Thwart out of the box. You can see these

RE: Reloading keystore - how to register a new TrusStore Manager for Tomcat?

/11/07, Mark Claassen [EMAIL PROTECTED] wrote: Humm. I don't think this is how the certificate system is supposed to be used. The intention is that the truststore handles certificates authorities you trust. For an example, let's switch to the browser. Browsers generally trust Verisgn

RE: Using Javac instead of JDT to compile JSPs

param-value1.5/param-value /init-param load-on-startup3/load-on-startup /servlet Hope that helps Lakshmi -Original Message- From: Mark Claassen [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 9:29 AM To: 'Tomcat Users List' Subject: Using Javac instead

Using Javac instead of JDT to compile JSPs

Has anyone tried to get the jasper compiler to be something other than the JDT? I tried several things, each of them not working. The docs say an alternative compiler can be specified, but makes no mention of how to specify it. This seems to be controlled by settings in the web.xml. Below is

RE: Using Javac instead of JDT to compile JSPs

mmons-logging-api.jar Thanks again, Mark -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 1:10 PM To: Tomcat Users List Subject: RE: Using Javac instead of JDT to compile JSPs From: Mark Claassen [mailto:[EMAIL PROTECTED] Subject: Using

RE: Using Javac instead of JDT to compile JSPs

Users List Subject: RE: Using Javac instead of JDT to compile JSPs From: Mark Claassen [mailto:[EMAIL PROTECTED] Subject: RE: Using Javac instead of JDT to compile JSPs Even with this fix, neither of the values below worked. param-valuecom.sun.tools.javac.main.Main/param-value

RE: Using Javac instead of JDT to compile JSPs

it. Still, I may investigate it further this weekend. -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 4:23 PM To: Tomcat Users List Subject: RE: Using Javac instead of JDT to compile JSPs From: Mark Claassen [mailto:[EMAIL PROTECTED

RE: Tomcat and OCSP

Now that I see Tomcat 6.0 is on it's way, I was wondering if OCSP is going to be included? This is being required by more and more people these days (like the US government). If there are no plans to include it yet, how can this issue be escalated? I see that OCSP support is bundled into the

RE: Random HTTP 502 errors

output on the connectors? Mark -Original Message- From: Mark Claassen [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 5:04 PM To: 'Tomcat Users List' Subject: Random HTTP 502 errors I was wondering if anyone could shed some light on some strange 502 errors I am having when going

RE: Tomcat and OCSP

Does anyone have any experience with this? -Original Message- From: Mark Claassen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 12:26 PM To: users@tomcat.apache.org Subject: Tomcat and OCSP Does the new support for OCSP in Java 5.0 have any impact on how certificates

Tomcat and OCSP

Does the new support for OCSP in Java 5.0 have any impact on how certificates are handled in Tomcat? http://java.sun.com/j2se/1.5.0/docs/guide/security/pki-tiger.html It looks like it might just work if it is set up right in the java property files. I checked the mailing list archives and found

RE: Restricting access to localhost for an HTTP connector - Email has different SMTP TO: and MIME TO: fields in the email addresses

=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / Leo From: Mark Claassen [mailto:[EMAIL PROTECTED] Sent: Thursday, June 08, 2006 10:51 AM To: 'Tomcat Users List' Subject: [SPAM

RE: Restricting access to localhost for an HTTP connector - Email has different SMTP TO: and MIME TO: fields in the email addresses

Andrew On 12/06/2006, at 3:08 PM, Peter Crowther wrote: From: Mark Claassen [mailto:[EMAIL PROTECTED] Say Tomcat is on a machine called TestMachine. If I put 127.0.0.1 in the address field, it accepts connections of the form http: //127.0.0.1/... only It does not accept connections from http

RE: Restricting access to localhost for an HTTP connector - Email has different SMTP TO: and MIME TO: fields in the email addresses

in the email addresses From: Mark Claassen [mailto:[EMAIL PROTECTED] Say Tomcat is on a machine called TestMachine. If I put 127.0.0.1 in the address field, it accepts connections of the form http: //127.0.0.1/... only It does not accept connections from http: //TestMachine/..., even though

Restricting access to localhost for an HTTP connector

Is there to configure an HTTP Connector to only allow connections from localhost? We have a server that has an HTTPS port that handles all public access. However, we would like to leave a non SSL port open for a monitoring program we have running on the same machine. We would like to not allow

RE: Restricting access to localhost for an HTTP connector

Thanks. I thought I heard that it was possible though the address, but was not sure. I read this in the docs, but I guess I didn't / don't understand the short explanation of "address". From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Thursday, June 08, 2006 1:24 PMTo: