[Bug 68696] New: Tomcat throws ClientAbortException: java.io.IOException: Broken pipe even the client request is complete successfully

https://bz.apache.org/bugzilla/show_bug.cgi?id=68696 Bug ID: 68696 Summary: Tomcat throws ClientAbortException: java.io.IOException: Broken pipe even the client request is complete successfully Product: Tomcat 9 V

[Bug 68495] Unable to find match between the canonical context and the URI presented by the user agent

https://bz.apache.org/bugzilla/show_bug.cgi?id=68495 --- Comment #11 from Remy Maucherat --- Ok so maybe there's still something with the query string then. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 68495] Unable to find match between the canonical context and the URI presented by the user agent

https://bz.apache.org/bugzilla/show_bug.cgi?id=68495 --- Comment #10 from Chuck Caldarale --- I was able to reproduce the problem on 9.0.85, but not on 9.0.86 (nor on 11.0.0-M17). Looks like something fixed it recently, but there's nothing obvious to me in the changelog for 9.0.86. -- You are r

[Bug 68495] Unable to find match between the canonical context and the URI presented by the user agent

https://bz.apache.org/bugzilla/show_bug.cgi?id=68495 --- Comment #9 from Noah Adams --- Before you ask, I just replicated this on a clean install of 9.0.85 RHEL 9 JDK 8 I only edited tomcat_users.xml to uncomment the admin user and change the password Note that to get the sample app to work wi

[Bug 68603] Request Context path and Query param gets replaced

https://bz.apache.org/bugzilla/show_bug.cgi?id=68603 --- Comment #15 from Noah Adams --- I believe this bug is a duplicate of https://bz.apache.org/bugzilla/show_bug.cgi?id=68495 and I uploaded a test case there. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 68495] Unable to find match between the canonical context and the URI presented by the user agent

https://bz.apache.org/bugzilla/show_bug.cgi?id=68495 Noah Adams changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME

[Bug 68495] Unable to find match between the canonical context and the URI presented by the user agent

https://bz.apache.org/bugzilla/show_bug.cgi?id=68495 --- Comment #7 from Noah Adams --- Created attachment 39607 --> https://bz.apache.org/bugzilla/attachment.cgi?id=39607&action=edit Sample web application to reproduce bug I am attaching a very simple web application that reliably reproduces

[Bug 68634] Forwards using custom response classes do not wait for session replication

https://bz.apache.org/bugzilla/show_bug.cgi?id=68634 --- Comment #2 from Remy Maucherat --- Ok, the ApplicationDispatcher forward does something different for a ResponseFacade, so it can mess up your timing. Obviously if the response is simply a ResponseFacade it gets suspended (pretending to be

(tomcat-tck) branch main updated: First pass at adding Servlet TCK support

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git The following commit(s) were added to refs/heads/main by this push: new 6517168 First pass at adding Servlet TCK support

Buildbot success in on tomcat-9.0.x

Build status: Build succeeded! Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/37/builds/878 Blamelist: Rémy Maucherat , remm Build Text: build successful Status Detected: restored build Build Source Stamp: [branch 9.0.x] 0640663aa94ea79cd70729fce23ac9378a82b57e Steps: wo

[Bug 68692] Http11Nio2Protocol not using provided executor

https://bz.apache.org/bugzilla/show_bug.cgi?id=68692 Remy Maucherat changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

(tomcat) branch 9.0.x updated: Implement ExecutorService

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/9.0.x by this push: new 0640663aa9 Implement ExecutorService 0640663aa9 is d

(tomcat) branch 10.1.x updated: Implement ExecutorService

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.1.x by this push: new 6d5c2d544d Implement ExecutorService 6d5c2d544d is

(tomcat) branch main updated: Additional Tomcat 11 change

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new 97fd44c75b Additional Tomcat 11 change 97fd44c75b is d

(tomcat) branch main updated: Implement ExecutorService

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new c0577c99c3 Implement ExecutorService c0577c99c3 is des

[Bug 68692] Http11Nio2Protocol not using provided executor

https://bz.apache.org/bugzilla/show_bug.cgi?id=68692 --- Comment #2 from Gabor Bodo --- Hi Remy, Thank you for the quick reply! Just to be clear, we are only passing this executor to a single connector, so it is used exclusively. I think that the current behaviour is a bit inconsistent in the