DO NOT REPLY [Bug 45051] New: Provide read only access for certain role in Administration webapp

https://issues.apache.org/bugzilla/show_bug.cgi?id=45051 Summary: Provide read only access for certain role in Administration webapp Product: Tomcat 5 Version: 5.5.26 Platform: All OS/Version: All Status: NEW

DO NOT REPLY [Bug 45052] New: Provide read only access for certain role in Manager webapp

https://issues.apache.org/bugzilla/show_bug.cgi?id=45052 Summary: Provide read only access for certain role in Manager webapp Product: Tomcat 5 Version: 5.5.26 Platform: All OS/Version: All Status: NEW Sev

Re: Potential problem with COMET & sendfile

On Tue, 2008-05-20 at 15:40 -0700, Alex Barclay wrote: > This works fine in the small. Here's what I'm seeing inside the tomcat > code. I was clued into this by not being able to find my socket (being > kept alive) because all of the pollers were on a "wait" call, rather > than on a "poll" call.

Re: svn commit: r658292 - /tomcat/tc6.0.x/trunk/STATUS.txt

On Wed, 2008-05-21 at 00:16 +0100, Mark Thomas wrote: > [EMAIL PROTECTED] wrote: > > * Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=42747 > >Use any META-INF/context.xml in a consistent manner and ensure it is > > used on > > @@ -95,4 +92,6 @@ > >-1: remm (would need convincing

DO NOT REPLY [Bug 45055] New: Tomcat Application custom load order

https://issues.apache.org/bugzilla/show_bug.cgi?id=45055 Summary: Tomcat Application custom load order Product: Tomcat 5 Version: 5.5.22 Platform: PC OS/Version: Windows XP Status: NEW Severity: enhancement Priority

svn commit: r658638 - /tomcat/tc6.0.x/trunk/STATUS.txt

Author: remm Date: Wed May 21 04:49:04 2008 New Revision: 658638 URL: http://svn.apache.org/viewvc?rev=658638&view=rev Log: - Votes. Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=6586

DO NOT REPLY [Bug 45059] New: http://www.servername.com/WEB-INF./web.xml

https://issues.apache.org/bugzilla/show_bug.cgi?id=45059 Summary: http://www.servername.com/WEB-INF./web.xml Product: Tomcat 5 Version: Unknown Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priori

DO NOT REPLY [Bug 45059] http://www.servername.com/WEB-INF./web.xml

https://issues.apache.org/bugzilla/show_bug.cgi?id=45059 Tim Funk <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED Re

Re: Potential problem with COMET & sendfile

Remy Maucherat wrote: On Tue, 2008-05-20 at 15:40 -0700, Alex Barclay wrote: This works fine in the small. Here's what I'm seeing inside the tomcat code. I was clued into this by not being able to find my socket (being kept alive) because all of the pollers were on a "wait" call, rather tha

Re: Potential problem with COMET & sendfile

I don't see any use case for Comet+sendfile make sense. but if you do it, you should ... set your sendfile stuff call CometEvent.close() . ie, the event shouldn't be cometized when doing sendfile, it makes zero sense since when the file is sent, the HTTP request is over. Filip Alex Barc

Re: Potential problem with COMET & sendfile

Filip Hanik - Dev Lists wrote: I don't see any use case for Comet+sendfile make sense. but if you do it, you should ... set your sendfile stuff call CometEvent.close() . ie, the event shouldn't be cometized when doing sendfile, it makes zero sense since when the file is sent, the HTTP req

Re: Potential problem with COMET & sendfile

Alex Barclay wrote: Filip Hanik - Dev Lists wrote: I don't see any use case for Comet+sendfile make sense. but if you do it, you should ... set your sendfile stuff call CometEvent.close() . ie, the event shouldn't be cometized when doing sendfile, it makes zero sense since when the file