DO NOT REPLY [Bug 7931] - A url that contains %2F in the path, tomcat returns 400 bad request.

2002-04-11 Thread bugzilla
/show_bug.cgi?id=7931 A url that contains %2F in the path, tomcat returns 400 bad request. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 7931] New: - A url that contains %2F in the path, tomcat returns 400 bad request.

2002-04-10 Thread bugzilla
/show_bug.cgi?id=7931 A url that contains %2F in the path, tomcat returns 400 bad request. Summary: A url that contains %2F in the path, tomcat returns 400 bad request. Product: Tomcat 4 Version: 4.0.4 Beta 2 Platform: All OS/Version

DO NOT REPLY [Bug 7344] - Tomcat appears to be case-sensitive with regard to the token Basic in Authorization request parameter

2002-03-23 Thread bugzilla
/show_bug.cgi?id=7344 Tomcat appears to be case-sensitive with regard to the token Basic in Authorization request parameter [EMAIL PROTECTED] changed: What|Removed |Added Status

DO NOT REPLY [Bug 7344] New: - Tomcat appears to be case-sensitive with regard to the token Basic in Authorization request parameter

2002-03-21 Thread bugzilla
/show_bug.cgi?id=7344 Tomcat appears to be case-sensitive with regard to the token Basic in Authorization request parameter Summary: Tomcat appears to be case-sensitive with regard to the token Basic in Authorization request parameter Product: Tomcat 4

DO NOT REPLY [Bug 7277] New: - request URI processing works wrong

2002-03-20 Thread bugzilla
/show_bug.cgi?id=7277 request URI processing works wrong Summary: request URI processing works wrong Product: Tomcat 4 Version: 4.0.4 Beta 1 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other

DO NOT REPLY [Bug 7277] - request URI processing works wrong

2002-03-20 Thread bugzilla
/show_bug.cgi?id=7277 request URI processing works wrong [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 6557] - isapi_redirector can not handle post request from netscape 4.7x

2002-03-19 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 7173] New: - Tomcat fails to respect HTTP HEAD request

2002-03-16 Thread bugzilla
/show_bug.cgi?id=7173 Tomcat fails to respect HTTP HEAD request Summary: Tomcat fails to respect HTTP HEAD request Product: Tomcat 4 Version: 4.0.3 Final Platform: Other OS/Version: Linux Status: NEW Severity: Minor Priority

DO NOT REPLY [Bug 7173] - Tomcat fails to respect HTTP HEAD request

2002-03-16 Thread bugzilla
/show_bug.cgi?id=7173 Tomcat fails to respect HTTP HEAD request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 5126] - Client request using HEAD results in a response body returned to client.

2002-03-16 Thread bugzilla
/show_bug.cgi?id=5126 Client request using HEAD results in a response body returned to client. [EMAIL PROTECTED] changed: What|Removed |Added CC

Re: DO NOT REPLY [Bug 5785] - XML request time attribute notgenerated correctly

2002-03-12 Thread Andreas Junghans
Hi, *moan* Now I have to convert HTML tags we have that use request-time attributes into custom tags so that we can give them request time attributes. *sigh* Is it going to change in 1.3? I mean, XSLT allows all *non*-XSLT tags to have the equivalent of request-time attributes. I guess I

Re: DO NOT REPLY [Bug 5785] - XML request time attributenotgenerated correctly

2002-03-12 Thread Khun Yee Fung
situations. Khun Yee [EMAIL PROTECTED] 03/12/02 03:46AM Hi, *moan* Now I have to convert HTML tags we have that use request-time attributes into custom tags so that we can give them request time attributes. *sigh* Is it going to change in 1.3? I mean, XSLT allows all *non*-XSLT tags to have

DO NOT REPLY [Bug 5785] - XML request time attribute not generated correctly

2002-03-11 Thread bugzilla
/show_bug.cgi?id=5785 XML request time attribute not generated correctly [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

Re: DO NOT REPLY [Bug 5785] - XML request time attribute notgenerated correctly

2002-03-11 Thread Khun Yee Fung
*moan* Now I have to convert HTML tags we have that use request-time attributes into custom tags so that we can give them request time attributes. *sigh* Is it going to change in 1.3? I mean, XSLT allows all *non*-XSLT tags to have the equivalent of request-time attributes. I guess I thought

DO NOT REPLY [Bug 6942] - getRequestURL does not return a port number is request scheme is different then http or https

2002-03-07 Thread bugzilla
/show_bug.cgi?id=6942 getRequestURL does not return a port number is request scheme is different then http or https [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 6942] New: - getRequestURL does not return a port number is request scheme is different then http or https

2002-03-06 Thread bugzilla
/show_bug.cgi?id=6942 getRequestURL does not return a port number is request scheme is different then http or https Summary: getRequestURL does not return a port number is request scheme is different then http or https Product: Tomcat 4 Version: 4.0.1

[4.0] [Seurity] Security problem when using the SecurityManager with a request dispatcher

2002-02-27 Thread Remy Maucherat
Hi, A security problem affecting Tomcat 4.0.2 (and all versions of 4.x) has been reported, which allows to get a request dispatcher to an URL outside of the context root. This is not a security problem when NOT using a security manager, since it is always possible to use direct filesystem

DO NOT REPLY [Bug 6610] - Request-Time Attribute Expressions in XML-Syntax JSPs not working

2002-02-25 Thread bugzilla
/show_bug.cgi?id=6610 Request-Time Attribute Expressions in XML-Syntax JSPs not working [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 6557] - isapi_redirector can not handle post request from netscape 4.7x

2002-02-25 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x --- Additional Comments From [EMAIL PROTECTED] 2002-02-25 20:30 --- i tried ajp13 for both tomcat3 and tomcat4. it seems worse, even ie can not connect to my servlet by calling both URLOpenStream()(an ie

RE: mod_jk suggestion, add request logging option

2002-02-22 Thread GOMEZ Henri
OK, I think that explains it. So mod_jk 2.0 and Ajp14 are still in development, and it may be a while before they are finished. What is the status of mod_jk (2) 1.2 and Ajp 14? My opinion: Jk2 supports all the features from jk1 ( and some more ). There are probably some new bugs and

Re: mod_jk suggestion, add request logging option

2002-02-22 Thread jean-frederic clere
GOMEZ Henri wrote: OK, I think that explains it. So mod_jk 2.0 and Ajp14 are still in development, and it may be a while before they are finished. What is the status of mod_jk (2) 1.2 and Ajp 14? My opinion: Jk2 supports all the features from jk1 ( and some more ). There are

RE: mod_jk suggestion, add request logging option

2002-02-22 Thread costinm
On Fri, 22 Feb 2002, GOMEZ Henri wrote: The only problem with jk2 is that it's only available for Apache 2.0, port to Apache 1.3 should be conducted... True. My focus was on cleaning up the code, and it was much easier with a single server. I don't think updating the other servers is very

RE: mod_jk suggestion, add request logging option

2002-02-22 Thread GOMEZ Henri
The only problem with jk2 is that it's only available for Apache 2.0, port to Apache 1.3 should be conducted... True. My focus was on cleaning up the code, and it was much easier with a single server. I don't think updating the other servers is very difficult. Hope so, maybe Apache 1.3 port

RE: mod_jk suggestion, add request logging option

2002-02-22 Thread GOMEZ Henri
So if I wanted to add the request logging feature to mod_jk 1.2 there is still time to do that? And should those changes be committed to the HEAD CVS branch of jakarta-tomcat-connectors? mod_jk 1.2 in JTC is not feature freeze, so let's commit there, some will port the update to mod_jk 2.0

DO NOT REPLY [Bug 6610] New: - Request-Time Attribute Expressions in XML-Syntax JSPs not working

2002-02-21 Thread bugzilla
/show_bug.cgi?id=6610 Request-Time Attribute Expressions in XML-Syntax JSPs not working Summary: Request-Time Attribute Expressions in XML-Syntax JSPs not working Product: Tomcat 4 Version: 4.0.2 Final Platform: All OS/Version: All

DO NOT REPLY [Bug 6557] - isapi_redirector can not handle post request from netscape 4.7x

2002-02-21 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x [EMAIL PROTECTED] changed: What|Removed |Added Component|Connectors |HTTP/1.1

DO NOT REPLY [Bug 6557] - isapi_redirector can not handle post request from netscape 4.7x

2002-02-21 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x --- Additional Comments From [EMAIL PROTECTED] 2002-02-21 16:19 --- Created an attachment (id=1222) dump of data thru http -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e

AW: mod_jk suggestion, add request logging option

2002-02-21 Thread Hans Schmid
von Glenn Nielsen Gesendet: Donnerstag, 21. Februar 2002 16:57 An: Tomcat Developers List Betreff: Re: mod_jk suggestion, add request logging option Updated list of fields for request logging. Timestamp worker host URI Status (OK, FAIL, etc) Latency (Time in ms or us to handle request

DO NOT REPLY [Bug 6557] - isapi_redirector can not handle post request from netscape 4.7x

2002-02-21 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x [EMAIL PROTECTED] changed: What|Removed |Added Component|HTTP/1.1 Connector |Connectors

Re: mod_jk suggestion, add request logging option

2002-02-21 Thread costinm
On Thu, 21 Feb 2002, Glenn Nielsen wrote: Currently mod_jk has four logging levels - (debug,info,error,emerg). I suggest a fifth log level be added called request. (debug, info, request, error, emerg) This log level would log each request with the following possible info, what info

RE: mod_jk suggestion, add request logging option

2002-02-21 Thread GOMEZ Henri
I suggest a fifth log level be added called request. (debug, info, request, error, emerg) This log level would log each request with the following possible info, what info is logged could be controlled by an new config option JkLogRequestFormat. +1, I don't know if I'll have time to help

RE: mod_jk suggestion, add request logging option

2002-02-21 Thread GOMEZ Henri
GOMEZ Henri wrote: These features could be added to mod_jk 1.2.0 (native) and 2.0.0 (native2) in jakarta-tomcat-connectors. What is the status of mod_jk (2) 1.2 and Ajp 14? mod_jk 1.2 is the original mod_jk from TC 3.3, with little cleanup. mod_jk 2.0 is a serious rewrite of mod_jk,

RE: mod_jk suggestion, add request logging option

2002-02-21 Thread GOMEZ Henri
OK, I think that explains it. So mod_jk 2.0 and Ajp14 are still in development, and it may be a while before they are finished. Depends on how many people will help, a known story ;) What about mod_jk 1.2, when will that be ready for production use? Ready to use, I'm using it since TC 4.0.2

Re: mod_jk suggestion, add request logging option

2002-02-21 Thread costinm
On Thu, 21 Feb 2002, Glenn Nielsen wrote: OK, I think that explains it. So mod_jk 2.0 and Ajp14 are still in development, and it may be a while before they are finished. What is the status of mod_jk (2) 1.2 and Ajp 14? My opinion: Jk2 supports all the features from jk1 ( and some more

AW: AW: mod_jk suggestion, add request logging option

2002-02-21 Thread Hans Schmid
-Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Glenn Nielsen Gesendet: Donnerstag, 21. Februar 2002 19:28 An: Tomcat Developers List Betreff: Re: AW: mod_jk suggestion, add request logging option Hans Schmid wrote: Hi, what

DO NOT REPLY [Bug 6557] New: - isapi_redirector can not handle post request from netscape 4.7x

2002-02-19 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x Summary: isapi_redirector can not handle post request from netscape 4.7x Product: Tomcat 3 Version: 3.3 Release Candidate 2 Platform: PC OS/Version

DO NOT REPLY [Bug 6557] - isapi_redirector can not handle post request from netscape 4.7x

2002-02-19 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x --- Additional Comments From [EMAIL PROTECTED] 2002-02-19 20:18 --- well, it was a netscape 4.7 issue. but the apache addon module of tomcat can handle such case. i think the isapi_redirect should do so

DO NOT REPLY [Bug 6557] - isapi_redirector can not handle post request from netscape 4.7x

2002-02-19 Thread bugzilla
/show_bug.cgi?id=6557 isapi_redirector can not handle post request from netscape 4.7x [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other |High

DO NOT REPLY [Bug 6531] New: - Request Dispatcher forward to j_security_check not working

2002-02-18 Thread bugzilla
/show_bug.cgi?id=6531 Request Dispatcher forward to j_security_check not working Summary: Request Dispatcher forward to j_security_check not working Product: Tomcat 4 Version: Nightly Build Platform: PC OS/Version: Windows NT/2K

DO NOT REPLY [Bug 6531] - Request Dispatcher forward to j_security_check not working

2002-02-18 Thread bugzilla
/show_bug.cgi?id=6531 Request Dispatcher forward to j_security_check not working [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 6515] New: - tomcat sets response headers in sub request

2002-02-17 Thread bugzilla
/show_bug.cgi?id=6515 tomcat sets response headers in sub request Summary: tomcat sets response headers in sub request Product: Tomcat 3 Version: 3.3 Final Platform: Other OS/Version: Other Status: NEW Severity: Major

DO NOT REPLY [Bug 6515] - tomcat sets response headers in sub request

2002-02-17 Thread bugzilla
/show_bug.cgi?id=6515 tomcat sets response headers in sub request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

Feature request - context as a vhost and a sub-dir

2002-02-03 Thread Deacon Marcus
Hi, Would it be possible for contexts to exist as a vhost (cntxt.domain.ext) and a sub-dir (www.domain.ext/cntxt) at the same time? Greetings, deacon Marcus -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]

DO NOT REPLY [Bug 6137] New: - Context Administration removes /ROOT instead of the specified context at first remove request

2002-01-30 Thread bugzilla
/show_bug.cgi?id=6137 Context Administration removes /ROOT instead of the specified context at first remove request Summary: Context Administration removes /ROOT instead of the specified context at first remove request Product: Tomcat 3 Version: 3.3

DO NOT REPLY [Bug 6137] - Context Administration removes /ROOT instead of the specified context at first remove request

2002-01-30 Thread bugzilla
/show_bug.cgi?id=6137 Context Administration removes /ROOT instead of the specified context at first remove request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

Update Request

2002-01-14 Thread Asar . Khan
Hi, When you are creating a default mail session you are using the Session.getDefaultInstance method - can this be changed to Session.getInstance. The reason being that the former seems to create an instance for the JVM and regardless of consequent changes to the SMTP host they are ignored.

DO NOT REPLY [Bug 5853] New: - Unable to get request parameters in the Error page for form based login

2002-01-14 Thread bugzilla
/show_bug.cgi?id=5853 Unable to get request parameters in the Error page for form based login Summary: Unable to get request parameters in the Error page for form based login Product: Tomcat 4 Version: Nightly Build Platform: All OS

DO NOT REPLY [Bug 5785] New: - XML request time attribute not generated correctly

2002-01-10 Thread bugzilla
/show_bug.cgi?id=5785 XML request time attribute not generated correctly Summary: XML request time attribute not generated correctly Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity

DO NOT REPLY [Bug 5742] New: - manager application hangs if the context is currently processing a request

2002-01-08 Thread bugzilla
/show_bug.cgi?id=5742 manager application hangs if the context is currently processing a request Summary: manager application hangs if the context is currently processing a request Product: Tomcat 4 Version: 4.0.1 Final Platform: PC

DO NOT REPLY [Bug 5742] - manager application hangs if the context is currently processing a request

2002-01-08 Thread bugzilla
/show_bug.cgi?id=5742 manager application hangs if the context is currently processing a request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

Fix for mod_webapp - warp connector operation under SSL client request

2002-01-03 Thread David Graff
the request. The only way that I've successfully been able to get mod_webapp to pass the correct scheme and SSL values is to do the following: cvs server: Diffing . Index: mod_webapp.c === RCS file: /home/cvspublic/jakarta-tomcat

DO NOT REPLY [Bug 5531] New: - ISAPI (iss_redirect.dll) doesn't forward the request

2001-12-20 Thread bugzilla
/show_bug.cgi?id=5531 ISAPI (iss_redirect.dll) doesn't forward the request Summary: ISAPI (iss_redirect.dll) doesn't forward the request Product: Tomcat 3 Version: 3.3 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity

DO NOT REPLY [Bug 5531] - ISAPI (iss_redirect.dll) doesn't forward the request

2001-12-20 Thread bugzilla
/show_bug.cgi?id=5531 ISAPI (iss_redirect.dll) doesn't forward the request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

Difference in the Request class between Tomcat 3.2 and Tomcat 3.3

2001-12-19 Thread Renato
Hi all, What happened to methods getRemoteAddr, getServerName, getServletPath in the Request class for Tomcat 3.3 ? I had an Interceptor written for Tomcat 3.2 that uses these methods within the Request. How can I access internal servlet information from Request int Tomcat 3.3 ? Thanks

Re: Difference in the Request class between Tomcat 3.2 and Tomcat 3.3

2001-12-19 Thread Renato
Just found it... they change names... ( silly me :)) ) On Wed Dec 19 11:54:57 2001, Renato [EMAIL PROTECTED] escreveu : Hi all, What happened to methods getRemoteAddr, getServerName, getServletPath in the Request class for Tomcat 3.3 ? I had an Interceptor written for Tomcat 3.2

DO NOT REPLY [Bug 4828] - getSession(true) gets last valid session iven if invalidated during same request

2001-12-09 Thread bugzilla
/show_bug.cgi?id=4828 getSession(true) gets last valid session iven if invalidated during same request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 5169] - If jsp_precompile is evalutated to be false, the request will be processed by the target JSP

2001-11-29 Thread bugzilla
/show_bug.cgi?id=5169 If jsp_precompile is evalutated to be false, the request will be processed by the target JSP [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 5169] New: - If jsp_precompile is evalutated to be false, the request will be processed by the target JSP

2001-11-28 Thread bugzilla
/show_bug.cgi?id=5169 If jsp_precompile is evalutated to be false, the request will be processed by the target JSP Summary: If jsp_precompile is evalutated to be false, the request will be processed by the target JSP Product: Tomcat 4 Version: 4.0.1

DO NOT REPLY [Bug 5171] New: - ContextManager: Error reading request, ignored - java.lang.ArrayIndexOutOfBoundsException: 2048

2001-11-28 Thread bugzilla
/show_bug.cgi?id=5171 ContextManager: Error reading request, ignored - java.lang.ArrayIndexOutOfBoundsException: 2048 Summary: ContextManager: Error reading request, ignored - java.lang.ArrayIndexOutOfBoundsException: 2048 Product: Tomcat 3 Version: 3.2

DO NOT REPLY [Bug 5171] - ContextManager: Error reading request, ignored - java.lang.ArrayIndexOutOfBoundsException: 2048

2001-11-28 Thread bugzilla
/show_bug.cgi?id=5171 ContextManager: Error reading request, ignored - java.lang.ArrayIndexOutOfBoundsException: 2048 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 5126] New: - Client request using HEAD results in a response body returned to client.

2001-11-27 Thread bugzilla
/show_bug.cgi?id=5126 Client request using HEAD results in a response body returned to client. Summary: Client request using HEAD results in a response body returned to client. Product: Tomcat 4 Version: 4.0.1 Final Platform: All OS

DO NOT REPLY [Bug 5126] - Client request using HEAD results in a response body returned to client.

2001-11-27 Thread bugzilla
/show_bug.cgi?id=5126 Client request using HEAD results in a response body returned to client. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 4828] New: - getSession(true) gets last valid session iven if invalidated during same request

2001-11-13 Thread bugzilla
/show_bug.cgi?id=4828 getSession(true) gets last valid session iven if invalidated during same request Summary: getSession(true) gets last valid session iven if invalidated during same request Product: Tomcat 4 Version: 4.0 Beta 7 Platform: PC

RE: How does Tomcat handle discarded-request

2001-11-02 Thread Hu, Xuebing
Thank you. Bill and Craig. David -- From: Bill Barker[SMTP:[EMAIL PROTECTED]] Reply To: Tomcat Developers List Sent: Thursday, November 01, 2001 6:28 PM To: Tomcat Developers List Subject: Re: How does Tomcat handle discarded-request Generally

How does Tomcat handle discarded-request

2001-11-01 Thread Hu, Xuebing
Hi, I issues to Tomcat one request which takes kind of long time to response, when the backend servlet or bean is working on the result, I just can not wait and clicked somewhere on my browser page to issue another request, in this case, I am wondering what Tomcat to do with the previous

Re: How does Tomcat handle discarded-request

2001-11-01 Thread Bill Barker
This depends on the version of Tomcat, and to some extent whether you are running Tomcat behind another web server. - Original Message - From: Hu, Xuebing [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 01, 2001 11:57 AM Subject: How does Tomcat handle discarded-request

RE: How does Tomcat handle discarded-request

2001-11-01 Thread Hu, Xuebing
Tomcat handle discarded-request This depends on the version of Tomcat, and to some extent whether you are running Tomcat behind another web server. - Original Message - From: Hu, Xuebing [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 01, 2001 11:57 AM Subject: How

RE: How does Tomcat handle discarded-request

2001-11-01 Thread Craig R. McClanahan
On Thu, 1 Nov 2001, Hu, Xuebing wrote: Date: Thu, 1 Nov 2001 17:03:29 -0500 From: Hu, Xuebing [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: RE: How does Tomcat handle discarded-request Thanks, Bill

RE: How does Tomcat handle discarded-request

2001-11-01 Thread Hu, Xuebing
at the browser side and I issues another request to TOMCAT Object result = workBean.doWork(param1, ..., paramn) ; // Is IOException thrown out here? out.println(result) ; % As per your explaination, is IOException thrown out on out.println()???, since it is JSP, so my

Re: How does Tomcat handle discarded-request

2001-11-01 Thread Bill Barker
cleanup. - Original Message - From: Hu, Xuebing [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Thursday, November 01, 2001 2:39 PM Subject: RE: How does Tomcat handle discarded-request Hi, Craig, Here is my skeleton jsp, jsp:useBean id=workBean class

DO NOT REPLY [Bug 4529] - webapp connector does not set isSecure() on request

2001-10-31 Thread bugzilla
/show_bug.cgi?id=4529 webapp connector does not set isSecure() on request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

How does Tomcat handle discarded-request

2001-10-31 Thread Hu, Xuebing
Hi, I issues to Tomcat one request which takes kind of long time to response, when the backend servlet or bean is working on the result, I just can not wait and clicked somewhere on my browser page to issue another request, in this case, I am wondering what Tomcat to do with the previous

Tomcat 3.2.3 Documentation update request.

2001-10-26 Thread Prasanna Uppaladadium
Hello. Could someone please update the Tomcat 3.2.3 documentation (http://jakarta.apache.org/tomcat/tomcat-3.2-doc/uguide/tomcat_ug.html)? In the section on server.xml, the description for Connector in the table in that section does not describe the inet option that can be used to make

DO NOT REPLY [Bug 4263] - Apache Tomcat service hangs after serving first request.

2001-10-18 Thread bugzilla
/show_bug.cgi?id=4263 Apache Tomcat service hangs after serving first request. --- Additional Comments From [EMAIL PROTECTED] 2001-10-18 09:13 --- Are you sure the first page you see wasn't served by your browser's cache ? I use the Tomcat as a sys service (installed through the installer

DO NOT REPLY [Bug 4263] - Apache Tomcat service hangs after serving first request.

2001-10-18 Thread bugzilla
/show_bug.cgi?id=4263 Apache Tomcat service hangs after serving first request. --- Additional Comments From [EMAIL PROTECTED] 2001-10-18 21:06 --- Dear Remy, I follow your step. Clear cache on my browser. I think you may right, the first page may come from browser cache. So, this time... I

DO NOT REPLY [Bug 4263] - Apache Tomcat service hangs after serving first request.

2001-10-18 Thread bugzilla
/show_bug.cgi?id=4263 Apache Tomcat service hangs after serving first request. [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Fwd: Tomcat's non-polymorphic request handler.]

2001-09-27 Thread Matt Larson
I sent this to the tomcat user group, but got no response. Comments? I'm having some difficulty with the polymorphic behavior of Tomcat's request handler. Consider the following: package RMS; import java.lang.Integer; public class TestPolyMorph { int i; String s; public void

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-26 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Additional Comments

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-26 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|tomcat- |[EMAIL PROTECTED

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-23 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters [EMAIL PROTECTED] changed: What|Removed |Added CC||sebastian.kanthak@muehlheim

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-21 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters --- Additional Comments From [EMAIL PROTECTED] 2001-09-21 09:23 --- But then, why do the values change, when we ADD a dummy url mapping (e.g. '/foobar/*') in the test-application's web.xml file? Adding, another url mapping shouldn't

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-21 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters --- Additional Comments From [EMAIL PROTECTED] 2001-09-21 11:41 --- All of your tests work for me. That is that the servlet_path is empty and everything is in the path_info just like it should be. The only way that I didn't get

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-21 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters --- Additional Comments From [EMAIL PROTECTED] 2001-09-21 14:13 --- Your remarks are corrct for the path_info and servet_path fields read from the ServletContext object of a running servlet. In the case where the url mapping

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-21 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-21 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

DO NOT REPLY [Bug 3727] - Switched included request parameters

2001-09-20 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters --- Additional Comments From [EMAIL PROTECTED] 2001-09-20 17:53 --- Since you have a servlet-mapping for /*, Tomcat's values are exactly what you would expect them to be.

DO NOT REPLY [Bug 3727] New: - Switched included request parameters

2001-09-19 Thread bugzilla
/show_bug.cgi?id=3727 Switched included request parameters Summary: Switched included request parameters Product: Tomcat 3 Version: 3.3 Beta 2 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other

DO NOT REPLY [Bug 3665] - Request Dispatching - Parameters are not properly set

2001-09-18 Thread bugzilla
/show_bug.cgi?id=3665 Request Dispatching - Parameters are not properly set [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED

DO NOT REPLY [Bug 3665] New: - Request Dispatching - Parameters are not properly set

2001-09-17 Thread bugzilla
/show_bug.cgi?id=3665 Summary: Request Dispatching - Parameters are not properly set Product: Tomcat 4 Version: 4.0 Release Candidate 2 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other

DO NOT REPLY [Bug 3665] - Request Dispatching - Parameters are not properly set

2001-09-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3665. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 3665] - Request Dispatching - Parameters are not properly set

2001-09-17 Thread bugzilla
--- Additional Comments From [EMAIL PROTECTED] 2001-09-17 17:11 --- The problem is that setting a request attribute to a null value is not legal (same for session attributes and servlet context attributes). Therefore, not setting the javax.servlet.include.path_info attribute is the appropriate

DO NOT REPLY [Bug 3641] - Bad value in query string parameter while forwarding request

2001-09-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3641. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: Tomcat 4 build from CVS this morning, bugs in request cookiehandling?

2001-09-05 Thread Craig R. McClanahan
On Wed, 5 Sep 2001, Glenn Nielsen wrote: Date: Wed, 05 Sep 2001 11:59:18 -0500 From: Glenn Nielsen [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 4 build from CVS this morning, bugs in request cookie handling? I built Tomcat 4 from CVS

Re: Tomcat 4 build from CVS this morning, bugs in request cookiehandling?

2001-09-05 Thread Glenn Nielsen
] To: [EMAIL PROTECTED] Subject: Tomcat 4 build from CVS this morning, bugs in request cookie handling? I built Tomcat 4 from CVS this morning and it looks like there may be a problem in how it is handling cookies, especially the JSESSIONID cookie. The HttpServletRequest seems

Re: Request: binary mod_webapp.so for Solaris built with -DEAPI

2001-08-31 Thread Pier Fumagalli
Eryq [EMAIL PROTECTED] wrote: I was using the mod_webapp.so connector for Solaris which I downloaded from apache.org All was going well until I rebuilt my Apache (1.3.20) with SSL support. Now I get: [warn] Loaded DSO libexec/mod_webapp.so uses plain Apache 1.3 API, this module might

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/request AccessInterceptor.java

2001-08-24 Thread nacho
nacho 01/08/24 16:58:51 Modified:src/share/org/apache/tomcat/request Tag: tomcat_32 AccessInterceptor.java Log: Fix for Bugzilla#2118 Incosistent behaviuor updating OriginalLocation in FormAuthHandler Class Reported by Juan Jose Muñoz ( jmartine

Request: binary mod_webapp.so for Solaris built with -DEAPI

2001-08-23 Thread Eryq
I was using the mod_webapp.so connector for Solaris which I downloaded from apache.org All was going well until I rebuilt my Apache (1.3.20) with SSL support. Now I get: [warn] Loaded DSO libexec/mod_webapp.so uses plain Apache 1.3 API, this module might crash under EAPI!

tomcat 4 request/response instrumentation

2001-08-17 Thread Kevin Seguin
something that i've started thinking about recently is how to provide hooks in tomcat 4 so that some statistics regarding request processing time could be collected. off of the top of my head, a couple of interesting stats might be average request processing time for all contexts (or webapps

Re: tomcat 4 request/response instrumentation

2001-08-17 Thread Pier P. Fumagalli
such that it could always log (or send events) at the beginning of a request and right before the response is sent? In TC4.0 valve are more-or-less like loggers. So if you put down a valve at the bottom of your Engine (the first root component in the component stack of Catralina), you'll end up

Re: tomcat 4 request/response instrumentation

2001-08-17 Thread Craig R. McClanahan
On Fri, 17 Aug 2001, Kevin Seguin wrote: something that i've started thinking about recently is how to provide hooks in tomcat 4 so that some statistics regarding request processing time could be collected. off of the top of my head, a couple of interesting stats might be average

<    3   4   5   6   7   8   9   >