This is an automated email from the ASF dual-hosted git repository.

markt-asf pushed a commit to branch 10.1.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git

commit 80acb52bb1214a0cd58e1527dcae47bd0b077b8b
Author: Mark Thomas <[email protected]>
AuthorDate: Thu Apr 30 17:01:20 2026 +0100

    Fix ordering
---
 java/org/apache/coyote/http2/LocalStrings.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/java/org/apache/coyote/http2/LocalStrings.properties 
b/java/org/apache/coyote/http2/LocalStrings.properties
index 3f9c623766..7b20ed97c6 100644
--- a/java/org/apache/coyote/http2/LocalStrings.properties
+++ b/java/org/apache/coyote/http2/LocalStrings.properties
@@ -98,9 +98,9 @@ stream.header.contentLength=Connection [{0}], Stream [{1}], 
The content length h
 stream.header.debug=Connection [{0}], Stream [{1}], HTTP header [{2}], Value 
[{3}]
 stream.header.duplicate=Connection [{0}], Stream [{1}], received multiple 
[{2}] headers
 stream.header.empty=Connection [{0}], Stream [{1}], Invalid empty header name
-stream.header.invalidConnect=Connection [{0}], Stream [{1}], The CONNECT 
request was invalid as neither :scheme nor :path should be present
 stream.header.inconsistentScheme=Connection [{0}], Stream [{1}], The scheme 
[{2}] is not consistent with the TLS enabled setting of [{3}]
 stream.header.invalid=Connection [{0}], Stream [{1}], The header [{2}] 
contained invalid value [{3}]
+stream.header.invalidConnect=Connection [{0}], Stream [{1}], The CONNECT 
request was invalid as neither :scheme nor :path should be present
 stream.header.noPath=Connection [{0}], Stream [{1}], The [:path] pseudo header 
was empty
 stream.header.required=Connection [{0}], Stream [{1}], One or more required 
headers was missing
 stream.header.te=Connection [{0}], Stream [{1}], HTTP header [te] is not 
permitted to have the value [{2}] in an HTTP/2 request


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to