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.git
The following commit(s) were added to refs/heads/main by this push:
new 72605f3df1 Use the better wording. Not just Range -> Content-Range
72605f3df1 is described below
commit 72605f3df1929b2a4a83725328ba1f3863101ebb
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Mon Dec 16 07:57:18 2024 +0000
Use the better wording. Not just Range -> Content-Range
---
conf/web.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/conf/web.xml b/conf/web.xml
index bafa023233..1e1df066ba 100644
--- a/conf/web.xml
+++ b/conf/web.xml
@@ -109,10 +109,10 @@
<!-- -->
<!-- allowPartialPut Should the server treat an HTTP PUT request -->
<!-- with a Content-Range header as a partial PUT? -->
- <!-- Note that while RFC 7233 clarified that -->
- <!-- Content-Range headers only valid for GET -->
- <!-- requests, RFC 9110 (which obsoletes RFC 7233) -->
- <!-- now allows partial puts. [true] -->
+ <!-- Note that while RFC 7231 clarified that such a -->
+ <!-- PUT with a Content-Range header field is a bad -->
+ <!-- request, RFC 9110 (which obsoletes RFC 7231) -->
+ <!-- now allows partial PUT. [true] -->
<!-- -->
<!-- directoryRedirectStatusCode -->
<!-- Status code to use for directory redirects. -->
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
