Bug report for Tomcat 7 [2020/04/19]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Native [2020/04/19]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Connectors [2020/04/19]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Taglibs [2020/04/19]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 9 [2020/04/19]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 8 [2020/04/19]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Modules [2020/04/19]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[GitHub] [tomcat] pzygielo commented on a change in pull request #275: BZ 59203 - interrupt tomcat threads instead of stopping

pzygielo commented on a change in pull request #275: BZ 59203 - interrupt tomcat threads instead of stopping URL: https://github.com/apache/tomcat/pull/275#discussion_r410846802 ## File path: java/org/apache/catalina/loader/WebappClassLoaderBase.java ## @@ -1813,35 +1813,4

Connection close for POST after successful expectation and status 302

Hi there, I noticed today TC behavior in TC 9 HEAD (but probably not specific to it), that a POST with "Expect: 100-Continue" first gets a correct status 100 response from TC. Then the client (an Apache reverse proxy) send the request body and the application correctly processes it and finally

Re: Connection close for POST after successful expectation and status 302

Communication trace for the sake of completenes: 1) Request POST /sid/D1_13.html HTTP/1.1 Host: z-web-01.some.domain:8143 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8

Re: Connection close for POST after successful expectation and status 302

It might be too simplistic, but the following at least stops the connection close (but I don't know, whether it also prevents it in cases where it should still be done): diff --git a/java/org/apache/coyote/http11/Http11Processor.java b/java/org/apache/coyote/http11/Http11Processor.java index

Re: Connection close for POST after successful expectation and status 302

Am 2020-04-19 um 14:40 schrieb Rainer Jung: I observed this when using Apache mod_proxy_http and mod_proxy_balancer with ping=5000, which wil add the expectation to any POST request. I wanted to tune Apache/Tomcat communication to use connections very long in order to reduce TLS handshakes duri

Re: Connection close for POST after successful expectation and status 302

Hi Michael, Am 19.04.2020 um 17:11 schrieb Michael Osipov: Am 2020-04-19 um 14:40 schrieb Rainer Jung: I observed this when using Apache mod_proxy_http and mod_proxy_balancer with ping=5000, which wil add the expectation to any POST request. I wanted to tune Apache/Tomcat communication to use

[tomcat-jakartaee-migration] 02/02: Test the migration of signed jar files

This is an automated email from the ASF dual-hosted git repository. ebourg pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat-jakartaee-migration.git commit f23a64982f793ebe43665466cf780f57979e63d4 Author: Emmanuel Bourg AuthorDate: Mon Apr 20 02:02:55 2020

[tomcat-jakartaee-migration] branch master updated (9cc4b6f -> f23a649)

This is an automated email from the ASF dual-hosted git repository. ebourg pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/tomcat-jakartaee-migration.git. from 9cc4b6f Remove unused methods in StringManager new 1738963 Remove the EC signature files

[tomcat-jakartaee-migration] 01/02: Remove the EC signature files

This is an automated email from the ASF dual-hosted git repository. ebourg pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat-jakartaee-migration.git commit 17389639f1f1236691f058d42f6e0b6d9b832894 Author: Emmanuel Bourg AuthorDate: Mon Apr 20 01:55:48 2020

[Bug 64355] Web application and Login page Is very slow and Login page to load is taking 5 minitues in Tomcat 9.0.34

https://bz.apache.org/bugzilla/show_bug.cgi?id=64355 Anantharao changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED