[Bug 63710] HTTP 304 NOT MODIFIED should not set Content-Length

2019-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63710 --- Comment #2 from Boris Petrov --- Is it possible that the default Tomcat configuration adds this header? When I run our integration tests (which use the embedded Tomcat), this header is not present in these responses. However, in

[Bug 63691] Add a no-op JarScanner

2019-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63691 --- Comment #2 from Igal Sapir --- (In reply to Mark Thomas from comment #1) > Why not just do > > System.setProperty("tomcat.util.scan.StandardJarScanFilter.jarsToSkip","*. > jar") ? IIRC then that still reads the directories and then

[Bug 63691] Add a no-op JarScanner

2019-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63691 Mark Thomas changed: What|Removed |Added OS||All --- Comment #1 from Mark Thomas

[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance

2019-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 --- Comment #1 from Mark Thomas --- It is expected that a class file is read once and once only when the class is loaded into memory. Therefore there is no point caching the contents of a class file. What use case requires that classes are

[Bug 63710] HTTP 304 NOT MODIFIED should not set Content-Length

2019-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63710 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

buildbot success in on tomcat-trunk

2019-08-30 Thread buildbot
The Buildbot has detected a restored build on builder tomcat-trunk while building tomcat. Full details are available at: https://ci.apache.org/builders/tomcat-trunk/builds/4573 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf946_ubuntu Build Reason: The

[tomcat] branch master updated: Add explicit config for ws upgrade handler

2019-08-30 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/master by this push: new f58a40f Add explicit config for ws upgrade

[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.

2019-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 Boris Petrov changed: What|Removed |Added Version|9.0.x |9.0.24 -- You are receiving this mail

[Bug 63710] New: HTTP 304 NOT MODIFIED should not set Content-Length

2019-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63710 Bug ID: 63710 Summary: HTTP 304 NOT MODIFIED should not set Content-Length Product: Tomcat 9 Version: 9.0.24 Hardware: PC OS: Linux Status: NEW

Re: [Bug 63699] craigwende...@gmail.com

2019-08-30 Thread Mark Thomas
On 30/08/2019 05:25, bugzi...@apache.org wrote: > https://bz.apache.org/bugzilla/show_bug.cgi?id=63699 And this idiot has been blocked from Bugzilla. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For