You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2022/09/01 06:34:23 UTC
[tomcat] branch 10.0.x updated: Correct order
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 10.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/10.0.x by this push:
new 18131346a9 Correct order
18131346a9 is described below
commit 18131346a9a7a69d44b21bc5e5f6a35ce62a47aa
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Thu Sep 1 07:34:07 2022 +0100
Correct order
---
webapps/docs/changelog.xml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml
index d9877bf77d..6f7dbeecf1 100644
--- a/webapps/docs/changelog.xml
+++ b/webapps/docs/changelog.xml
@@ -203,16 +203,16 @@
errors) via a <code>UserDataHelper</code> to broadly align it with the
behaviour of HTTP/1.1 for parsing issues and exceeding limits. (markt)
</fix>
- <fix>
- <bug>66240</bug>: Avoid int overflow when parsing octets by limiting
- the maximum value to 255. Based on a PR <pr>548</pr> by Stefan Mayr.
- (lihan)
- </fix>
<fix>
<bug>66236</bug>: Implement support for the special values zero and
minus one when configuring <code>maxSavePostSize</code> for a Connector
when used in conjunction with TLS renegotiation. (markt)
</fix>
+ <fix>
+ <bug>66240</bug>: Avoid int overflow when parsing octets by limiting
+ the maximum value to 255. Based on a PR <pr>548</pr> by Stefan Mayr.
+ (lihan)
+ </fix>
</changelog>
</subsection>
<subsection name="Jasper">
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org