To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project tomcat-tc7.0.x-test-nio has an issue affecting its community
https://bz.apache.org/bugzilla/show_bug.cgi?id=62620
Bug ID: 62620
Summary: Async servlet over HTTP/2 large write data corrupted
Product: Tomcat 9
Version: 9.0.10
Hardware: PC
OS: Linux
Status: NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=62603
--- Comment #7 from Jordi ---
Unable to reproduce the error with 8.5.33
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe,
Github user markt-asf commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/117#discussion_r20982
--- Diff: webapps/docs/introduction.xml ---
@@ -89,6 +80,122 @@ same as $CATALINA_HOME.
+
+ Throughout the documentation, there
Github user m-czernek commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/117#discussion_r209548456
--- Diff: webapps/docs/introduction.xml ---
@@ -89,6 +80,122 @@ same as $CATALINA_HOME.
+
+ Throughout the documentation, there
Author: markt
Date: Mon Aug 13 09:44:01 2018
New Revision: 1837934
URL: http://svn.apache.org/viewvc?rev=1837934=rev
Log:
Restore MSDN to the tools list as Microsoft have fixed the issues around
renewals
Added:
tomcat/site/trunk/docs/res/images/msdn.png (with props)
Github user m-czernek commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/117#discussion_r209532683
--- Diff: webapps/docs/introduction.xml ---
@@ -89,6 +80,122 @@ same as $CATALINA_HOME.
+
+ Throughout the documentation, there
Author: markt
Date: Mon Aug 13 07:51:27 2018
New Revision: 1837924
URL: http://svn.apache.org/viewvc?rev=1837924=rev
Log:
Make the isLocked() method of the LockOutRealm public and expose the method via
JMX.
Modified:
tomcat/tc8.5.x/trunk/ (props changed)
This is a question for the users mailing list, not the dev list.
Mark
On 13/08/18 06:01, Jeet Kaushik wrote:
> Hi,
>
> We are facing 400 bad request issues while upgrading to tomcat 8.0.53.
> Earlier we were using tomcat 8.0.39, where our application was working fine,
> but after
