head 1.7; access; symbols pkgsrc-2013Q2:1.7.0.50 pkgsrc-2013Q2-base:1.7 pkgsrc-2012Q4:1.7.0.48 pkgsrc-2012Q4-base:1.7 pkgsrc-2011Q4:1.7.0.46 pkgsrc-2011Q4-base:1.7 pkgsrc-2011Q2:1.7.0.44 pkgsrc-2011Q2-base:1.7 pkgsrc-2009Q4:1.7.0.42 pkgsrc-2009Q4-base:1.7 pkgsrc-2008Q4:1.7.0.40 pkgsrc-2008Q4-base:1.7 pkgsrc-2008Q3:1.7.0.38 pkgsrc-2008Q3-base:1.7 cube-native-xorg:1.7.0.36 cube-native-xorg-base:1.7 pkgsrc-2008Q2:1.7.0.34 pkgsrc-2008Q2-base:1.7 pkgsrc-2008Q1:1.7.0.32 pkgsrc-2008Q1-base:1.7 pkgsrc-2007Q4:1.7.0.30 pkgsrc-2007Q4-base:1.7 pkgsrc-2007Q3:1.7.0.28 pkgsrc-2007Q3-base:1.7 pkgsrc-2007Q2:1.7.0.26 pkgsrc-2007Q2-base:1.7 pkgsrc-2007Q1:1.7.0.24 pkgsrc-2007Q1-base:1.7 pkgsrc-2006Q4:1.7.0.22 pkgsrc-2006Q4-base:1.7 pkgsrc-2006Q3:1.7.0.20 pkgsrc-2006Q3-base:1.7 pkgsrc-2006Q2:1.7.0.18 pkgsrc-2006Q2-base:1.7 pkgsrc-2006Q1:1.7.0.16 pkgsrc-2006Q1-base:1.7 pkgsrc-2005Q4:1.7.0.14 pkgsrc-2005Q4-base:1.7 pkgsrc-2005Q3:1.7.0.12 pkgsrc-2005Q3-base:1.7 pkgsrc-2005Q2:1.7.0.10 pkgsrc-2005Q2-base:1.7 pkgsrc-2005Q1:1.7.0.8 pkgsrc-2005Q1-base:1.7 pkgsrc-2004Q4:1.7.0.6 pkgsrc-2004Q4-base:1.7 pkgsrc-2004Q3:1.7.0.4 pkgsrc-2004Q3-base:1.7 pkgsrc-2004Q2:1.7.0.2 pkgsrc-2004Q2-base:1.7 pkgsrc-2004Q1:1.6.0.12 pkgsrc-2004Q1-base:1.6 pkgsrc-2003Q4:1.6.0.10 pkgsrc-2003Q4-base:1.6 netbsd-1-6-1:1.6.0.6 netbsd-1-6-1-base:1.6 netbsd-1-6:1.6.0.8 netbsd-1-6-RELEASE-base:1.6 pkgviews:1.6.0.4 pkgviews-base:1.6 buildlink2:1.6.0.2 buildlink2-base:1.6 netbsd-1-5-PATCH003:1.6 netbsd-1-5-PATCH001:1.5 netbsd-1-5-RELEASE:1.2 netbsd-1-4-PATCH003:1.2; locks; strict; comment @# @; 1.7 date 2004.04.29.18.24.55; author erh; state dead; branches; next 1.6; 1.6 date 2001.06.21.13.12.27; author abs; state Exp; branches; next 1.5; 1.5 date 2001.04.03.11.05.25; author wennmach; state Exp; branches; next 1.4; 1.4 date 2001.03.29.23.26.25; author jwise; state Exp; branches; next 1.3; 1.3 date 2001.03.28.02.46.09; author jwise; state dead; branches; next 1.2; 1.2 date 2000.09.03.13.38.50; author wiz; state Exp; branches; next 1.1; 1.1 date 2000.05.31.22.47.28; author jwise; state Exp; branches; next ; desc @@ 1.7 log @Update the jakarta-tomcat package to Tomcat 5.0.19. This is a Java Servlet 2.4 and JSP 2.0 server. @ text @$NetBSD: patch-ac,v 1.6 2001/06/21 13:12:27 abs Exp $ --- src/share/org/apache/tomcat/task/ApacheConfig.java.orig Tue Dec 12 22:52:08 2000 +++ src/share/org/apache/tomcat/task/ApacheConfig.java @@@@ -115,8 +115,8 @@@@ } else { // XXX XXX change it to mod_jserv_${os.name}.so, put all so in tomcat // home - pw.println("LoadModule jserv_module libexec/mod_jserv.so"); - mod_jk.println("LoadModule jk_module libexec/mod_jk.so"); + pw.println("LoadModule jserv_module lib/httpd/mod_jserv.so"); + mod_jk.println("LoadModule jk_module lib/httpd/mod_jk.so"); mod_jk.println(); mod_jk.println("JkWorkersFile " + new File(tomcatHome, WORKERS_CONFIG)); mod_jk.println("JkLogFile " + new File(tomcatHome, JK_LOG_LOCATION)); @ 1.6 log @Switch to a dynamic PLIST so we can install against jdk or sun-jdk @ text @d1 1 a1 1 $NetBSD$ @ 1.5 log @RCS Id police @ text @d3 13 a15 27 --- src/etc/workers.properties.orig Thu Mar 29 14:16:09 2001 +++ src/etc/workers.properties Thu Mar 29 14:16:41 2001 @@@@ -40,20 +40,20 @@@@ # installed tomcat. This is where you have your conf, webapps and lib # directories. # -workers.tomcat_home=c:\jakarta-tomcat +workers.tomcat_home=@@PREFIX@@/tomcat # # workers.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # -workers.java_home=c:\jdk1.2.2 +workers.java_home=@@JAVA_HOME@@ # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something different elsewhere. # -ps=\ -# ps=/ +# ps=\ +ps=/ # #------ ADVANCED MODE ------------------------------------------------ @ 1.4 log @Ease out-of-the-box integration with mod_jk (pkgsrc/www/ap-jk): * include a workers.properties which works out of the box -- this file may be better off as part of the ap-jk package, even though it is somewhat tomcat-specific. I'll give this possibility more thought. * modify the apache config file fragment generator which runs on tomcat startup to generate an Include-able apache config file fragment which works out of the box to laod mod_jk. @ text @d1 2 @ 1.3 log @Update jakarta-tomcat to version 3.2.1. Changes in the package since version 3.1.1 (the last pkgsrc version): ===================================================================== * tomcat is now always installed under ${PREFIX}/tomcat. Making ${TOMCAT_HOME} configurable added much complexity for not real gain. It had been my intention to aim for a hier(7) like install for tomcat with this version, but at this point there are way to many hard-coded relative paths (relative to tomcat.home) in tomcat, and in addition, all of the (quite good, really) documentation assumes the standard install paths. Note that the previous default value of ${TOMCAT_HOME} was ${PREFIX}/jakarta/tomcat. * an rc.subr compatible (but not requiring) startup script is now installed as ${PREFIX}/etc/rc.d/tomcat. * if Sun's JSSE (Java Secure Socket Extensions) is in ${CLASSPATH} when the pkg is built, tomcat will be built with support for SSL in the standalone server mode. This soft dependency will be replaced by a hard dependency as soon as I get a chance to import a JSSE package (soon). * likewise, I will import an ap-jk package for the new apache connector (mod_jk) soon. ap-jserv continues to be usable for this purpose. Changes in tomcat itself since version 3.1.1: ============================================= New in tomcat-3.2.1: -------------------- Tomcat 3.2.1 is a maintenance and bug fix release, based on the Tomcat 3.2 (final) code base. The following changes are included: - Disallowed requesting JSP pages under the WEB-INF directory (/WEB-INF/dummy.jsp). Previously, only requests for static files were being disallowed. - The JDBCRealm request interceptor will now log the description of any JDBC exception that occurs, to aid in debugging. SECURITY VULNERABILITIES FIXED IN TOMCAT 3.2.1 (note that these fixes were also made to the tomcat-3.1 branch in tomcat 3.1.1) Protection of Resources in /WEB-INF and /META-INF Directories The servlet specification prohibits servlet containers from serving resources in the /WEB-INF and /META-INF directories of a web application archive directly to clients. In Tomcat 3.2, this means that URLs like: http://localhost:8080/examples/WEB-INF/web.xml will return an error message, rather than the contents of your deployment descriptor. However, there is a vulnerability in Tomcat 3.2 that exposes this information if the client requests a URL like this instead: http://localhost:8080/examples//WEB-INF/web.xml (note the double slash before "WEB-INF"). This vulnerability has been corrected in Tomcat 3.2.1. Show Source Vulnerability The example application delivered with Tomcat 3.2 included a mechanism to display the source code for the JSP page examples. This mechanism could be used to bypass the restrictions on displaying sensitive information in the WEB-INF and META-INF directories. This vulnerability has been removed. New in tomcat-3.2: ------------------ Tomcat 3.2 is mainly a performance tune-up release, although a few new features have been added. - Support for mod_jk, which is a replacement to the elderly mod_jserv, has had several bugs fixed and has received much more testing. It is now recommended that all users use mod_jk instead of mod_jserv. - Support JAXP-based XML parser independence. - New and often requested "how-to" documents covering the following topics: - Configuring workers.properties - IIS and Netscape configuration - Running tomcat inside an IIS or Netscape process - Running Tomcat as a Windows NT service - Configuring a JDBC realm - Configuring mod_jk - First round of policy-based security support intended for running untrusted code inside of Tomcat. Interested users should test this support and post feedback to the Tomcat users mailing list. - SSL support for standalone Tomcat. (Preliminary support first appeared in 3.1, but the support in 3.2 has received more testing and documentation support). - Thread reuse is now enabled by default. The thread pool support code was part of 3.1, but not enabled since it was new. - Support for plug-able session managers. Unfortunately, no how-to documents that support this functionality exist (yet). For the adventurous, be aware that the interface that allows administrators to plug session managers is the normal Interceptor interface. - An almost total rewrite of the HTTP request handling now results in improved performance when running Tomcat stand-alone. - Significantly reduced garbage collection. - The code underwent a refactoring effort resulting in improved readability. - And of course, hundreds of miscellaneous improvements and fixes. @ text @d1 8 a8 5 $NetBSD: patch-ac,v 1.2 2000/09/03 13:38:50 wiz Exp $ --- src/shell/tomcat.sh.orig Wed May 31 15:43:29 2000 +++ src/shell/tomcat.sh Wed May 31 15:43:58 2000 @@@@ -107,7 +107,8 @@@@ fi d10 6 a15 5 if [ "$oldCP" != "" ]; then - CLASSPATH=${CLASSPATH}:${oldCP} +# CLASSPATH=${CLASSPATH}:${oldCP} + CLASSPATH=${oldCP}:${CLASSPATH} fi d17 11 a27 1 export CLASSPATH @ 1.2 log @add RCS Ids @ text @d1 1 a1 1 $NetBSD$ @ 1.1 log @Modify tomcat startup process slightly -- now we add tomcat specific jar files at the _end_ of the CLASSPATH instead of the start so that users can override selected functionality. For example, cocoon needs to override tomcat's own XML parsing with that from Xerces-J if you want PDF generation from XSL Formatting Objects to work. @ text @d1 1 @