BugRat Report #560 has been filed.

2000-12-09 Thread BugRat Mail System
Bug report #560 has just been filed. You can view the report at the following URL: http://znutar.cortexity.com/BugRatViewer/ShowReport/560 REPORT #560 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: medium Severity: serious

pre compile

2000-12-09 Thread Cengiz Kayay
Hi all Does anybody know how do i compile all jsps at once from command line or whatever. I do not want to go to each page to have them compiled. Thanks = Cengiz Kayay WebObjects/JAVA Consultant __ Do You Yahoo!? Yahoo! Shopping -

RE: Handler/ServletWrapper/Error handling

2000-12-09 Thread cmanolache
Hi Larry, Suggestion 1) In Handler and ServletWrapper some calls are made to contextM.handleStatus() and contextM.handleError(). I think it would be an improvement to add handlerStatus() and handleError() to Handler, which would make the call to contextM.handleXXX. This would allow,

Re: how to maintain session between HTTP and HTTPS?

2000-12-09 Thread Paul Frieden
In a load balanced environment, this is tricky with people behind a IP randomizing proxy (like AOL). If you use all SSL, the load balancer can track the SSL session ID across different IPs. If you use all non-SSL, you can track with a cookie. You can use IP based sticky if the IP stays the

[PROPOSAL] JSSI for Tomcat

2000-12-09 Thread Hans Bergsten
After seeing a number of users on the TC user list asking about support for servlet tags and NCSA SSI directives, I decided to port Apache JSSI to Tomcat. Now it's basically done for TC 3.2, and the question is what to do with it ;-) If anyone is interested in this, I propose the following:

Re: [PROPOSAL] JSSI for Tomcat

2000-12-09 Thread Jon Stevens
on 12/9/2000 1:48 PM, "Hans Bergsten" [EMAIL PROTECTED] wrote: After seeing a number of users on the TC user list asking about support for servlet tags and NCSA SSI directives, I decided to port Apache JSSI to Tomcat. Now it's basically done for TC 3.2, and the question is what to do with it

Re: [PROPOSAL] JSSI for Tomcat

2000-12-09 Thread Hans Bergsten
Jon Stevens wrote: [...] 1) Make this a new Jakarta subproject, named jakarta-jssi. The reason for this is that it's an optional module and it can live its own life outside the container development. Note! This requires approval by the PMC, but I want to see what this group thinks

RE: Handler/ServletWrapper/Error handling

2000-12-09 Thread Larry Isaacs
Easy to do, seems a good idea. What about adding handleInitException() and handleServiceException() - since a ClassNotFound will have different effects ( 404 if in init, normal error if in service - the first means the servlet wasn't found, the second may happen if the servlet does a

Re: [PROPOSAL] JSSI for Tomcat

2000-12-09 Thread Jon Stevens
on 12/9/2000 3:55 PM, "Hans Bergsten" [EMAIL PROTECTED] wrote: I know the migration of Java Apache projects has been discussed, but I have not seen a formal decision being made by PMC. So I like to run it by the PMC anyway, but based on what you say it sounds like it will not be any problem

Re: [PROPOSAL] JSSI for Tomcat

2000-12-09 Thread Craig R. McClanahan
Jon Stevens wrote: on 12/9/2000 3:55 PM, "Hans Bergsten" [EMAIL PROTECTED] wrote: I know the migration of Java Apache projects has been discussed, but I have not seen a formal decision being made by PMC. So I like to run it by the PMC anyway, but based on what you say it sounds like it

Re: [PROPOSAL] JSSI for Tomcat

2000-12-09 Thread Hans Bergsten
"Craig R. McClanahan" wrote: [...] If it is Tomcat-specific, is there any reason it really needs to be a separate Jakarta project at all? Why not just absorb it into Tomcat? In terms of CVS repositories, if the amount of version-dependent code is large it would be easier just to put it in

cvs commit: jakarta-tomcat-4.0/webapps/examples/WEB-INF/classes/examples ShowSource.java

2000-12-09 Thread craigmcc
craigmcc00/12/09 19:12:19 Modified:webapps/examples/WEB-INF/classes/examples ShowSource.java Log: Fix a security vulnerability. The "ShowSource" custom tag, in conjunction with the "/examples/jsp/source.jsp" page, could be used to expose sensitive data in the WEB-INF and

Re: [PROPOSAL] JSSI for Tomcat

2000-12-09 Thread Jon Stevens
on 12/9/2000 6:21 PM, "Craig R. McClanahan" [EMAIL PROTECTED] wrote: If it is Tomcat-specific, is there any reason it really needs to be a separate Jakarta project at all? Why not just absorb it into Tomcat? Problem with that in my eyes is that Tomcat is supposed to be the reference

Re: cvs commit:jakarta-tomcat/src/examples/WEB-INF/classes/examples ShowSource.java

2000-12-09 Thread Jon Stevens
on 12/9/2000 7:07 PM, "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: +(jspFile.toUpperCase().indexOf("/WEB-INF/") != 0) || +(jspFile.toUpperCase().indexOf("/META-INF/") != 0)) Seems like it would be better to define this as a constant somewhere... public static final

Re: cvs commit:jakarta-tomcat/src/examples/WEB-INF/classes/examples ShowSource.java

2000-12-09 Thread Craig R. McClanahan
Jon Stevens wrote: on 12/9/2000 7:07 PM, "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: +(jspFile.toUpperCase().indexOf("/WEB-INF/") != 0) || +(jspFile.toUpperCase().indexOf("/META-INF/") != 0)) Seems like it would be better to define this as a constant

cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java ParserXJspSaxHandler.java

2000-12-09 Thread pierred
pierred 00/12/09 21:56:44 Modified:jasper/src/share/org/apache/jasper Constants.java jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java ParserXJspSaxHandler.java Log: Take 2 on the

Re: cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java ParserXJspSaxHandler.java

2000-12-09 Thread Hans Bergsten
[EMAIL PROTECTED] wrote: pierred 00/12/09 21:56:44 Modified:jasper/src/share/org/apache/jasper Constants.java jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java

Re: cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java ParserXJspSaxHandler.java

2000-12-09 Thread Pierre Delisle
Hans Bergsten wrote: [EMAIL PROTECTED] wrote: pierred 00/12/09 21:56:44 Modified:jasper/src/share/org/apache/jasper Constants.java jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java

Re: cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java ParserXJspSaxHandler.java

2000-12-09 Thread Pierre Delisle
Hans Bergsten wrote: Pierre Delisle wrote: Hans Bergsten wrote: [EMAIL PROTECTED] wrote: pierred 00/12/09 21:56:44 Modified:jasper/src/share/org/apache/jasper Constants.java jasper/src/share/org/apache/jasper/compiler

Re: cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler BeanGenerator.java JspParseEventListener.java ParserXJspSaxHandler.java

2000-12-09 Thread Hans Bergsten
Pierre Delisle wrote: Hans Bergsten wrote: [...] In general, I prefer imports for the reason you mention; it makes it easier to see all dependencies. In generated JSP compilation classes, the important thing is not to have other complete package imports than the ones in the spec, but