pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2002-04-19	Missed cvs rm of this file.	jwise	1	-12/+0

2002-04-19	Update jakarta-servletapi, jakarta-tomcat, and ap-jk to version 3.2.4.	jwise	2	-7/+7
	We are not advancing to the 3.3 or 4.0 branches at the moment, as neither will work with our native JDK without a lot more work. Changes since Tomcat 3.2.3 (the last pkgsrc version): 7.1 Fixes and Enhancements in Release 3.2.4 This section highlights the bugs fixed in this release. - Cookie name expires is a reserved token (#1114) - Thread initialization problem in thread pool (#1745) - AJP12 returned invalid HTTP headers when redirecting to very long URLS (#2333) - Fixed casting problem in JspFactoryImpl.getPageContext(). (#4260) - Setting sesstion-timeout in web.xml did not prevent sessions from timing out. (#4412) - Fixed race condition in ServerSocketFactory.getDefault(). (#4418) - Removed the restrictions on encoded spcecial characters in URLs that was added as a security precaution in 3.2.3. The encoded special characters are not decoded and remain the URL and path info returned to servlets. - Jk_nt_service now supports the ability to be restarted automatically by the Windows 2000 service control manager if Tomcat terminates abnormally. - Fixed invalid servlet mapping in web.xml generated by JspC (#3474, #3499) - Added findResource() and findResources() to AdaptiveClassLoader12 - A Date: HTTP header is now sent in responses when running stand alone. (#345) - Simple held on to a reference to removed objects preventing garbage collection. - Tomcat 3.2.4 now ships with JAXP 1.1. Prior releases used JAXP 1.0.1. Tomcat 3.2.4 remains completely compatible with the older version of JAXP and there is no requirement for users to upgrade to JAXP 1.1 unless their applications require the new version. - Fixed NullPointerException in HttpConnectionHandler. (#4577) 7.2 Security Vulnerabilities fixed in Tomcat 3.2.4 The randomness of generated session ids has been enhanced to prevent the generation of guessable ids.
2002-02-28	Note that these modules only work with Apache 1.3.* and not the forthcoming	jlam	1	-2/+2
	Apache 2.x servers.
2001-11-01	Move pkg/ files into package's toplevel directory	zuntum	3	-2/+2

2001-09-27	Mechanical changes to 375 files to change dependency patterns of the form	jlam	1	-2/+2
	foo-* to foo-[0-9]. This is to cause the dependencies to match only the packages whose base package name is "foo", and not those named "foo-bar". A concrete example is p5-Net- matching p5-Net-DNS as well as p5-Net. Also change dependency examples in Packages.txt to reflect this.
2001-05-20	Make all the ap-* packages work with apache6 as well as apache	jonb	1	-2/+2
	(except for ap-ssl, of course)
2001-05-12	USE_PERL is not the correct name of the variable. Remove it anyway and	jlam	1	-2/+3
	properly add a build depend on perl so that Apache's apxs will work.
2001-04-27	Make this pkg build with sun-jre/jdk: it comes with a include/linux dir,	hubertf	1	-2/+4
	so we need to set -I to get the headers there. (There's some -I.../include/netbsd already, i guess that's for a NetBSD-native JDK or something, not touching that one). Adresses PR 12571 by Omar Asfour <oasfour@email.com>
2001-04-21	Drop remaining uses of DIGEST_FILE (which were bogus, anyway)	wiz	1	-3/+1

2001-04-17	+ move the distfile digest/checksum value from files/md5 to distinfo	agc	2	-3/+4
	+ move the patch digest/checksum values from files/patch-sum to distinfo
2001-03-29	Initial import of ap-jk-3.2.1, the next generation connector for accessing	jwise	5	-0/+57
	Jakarta Tomcat of JServ from Apache. Some more information: What is mod_jk? mod_jk is a replacement to the elderly mod_jserv. It is a completely new Tomcat-Apache plugin that handles the communication between Tomcat and Apache Why mod_jk? Several reasons: mod_jserv was too complex. Because it was ported from Apache/JServ, it brought with it lots of JServ specific bits that aren't needed by Apache. mod_jserv supported only Apache. Tomcat supports many web servers through a compatibility layer named the jk library. Supporting two different modes of work became problematic in terms of support, documentation and bug fixes. mod_jk should fix that. The layered approach provided by the jk library makes it easier to support both Apache1.3.x and Apache2.xx. Better support for SSL. mod_jserv couldn't reliably identify whether a request was made via HTTP or HTTPS. mod_jk can, using the newer Ajpv13 protocol.