This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 11.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/11.0.x by this push:
new 72184f3409 update terms about partial PUT - a PUT with Content-Range
Header (#795)
72184f3409 is described below
commit 72184f3409684653a9ad6787cb188a590b3bf84f
Author: Chenjp <[email protected]>
AuthorDate: Mon Dec 16 15:50:35 2024 +0800
update terms about partial PUT - a PUT with Content-Range Header (#795)
RFC7231#4.3.4: An origin server that allows PUT on a given target resource
MUST send a 400 (Bad Request) response to a PUT request that contains a
Content-Range header field
---
conf/web.xml | 10 +++++-----
webapps/docs/default-servlet.xml | 8 ++++----
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/conf/web.xml b/conf/web.xml
index 08a32c2dca..9c95b04d03 100644
--- a/conf/web.xml
+++ b/conf/web.xml
@@ -114,11 +114,11 @@
<!-- listings is enabled? [true] -->
<!-- -->
<!-- allowPartialPut Should the server treat an HTTP PUT request -->
- <!-- with a Range header as a partial PUT? Note -->
- <!-- that while RFC 7233 clarified that Range -->
- <!-- headers only valid for GET requests, RFC 9110 -->
- <!-- (which obsoletes RFC 7233) now allows partial -->
- <!-- puts. [true] -->
+ <!-- with a Content-Range header as a partial PUT? -->
+ <!-- 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. -->
diff --git a/webapps/docs/default-servlet.xml b/webapps/docs/default-servlet.xml
index 8b906081c9..8616351af6 100644
--- a/webapps/docs/default-servlet.xml
+++ b/webapps/docs/default-servlet.xml
@@ -209,10 +209,10 @@ Tomcat.</p>
Should the server list all directories before all files. [false]
</property>
<property name="allowPartialPut">
- Should the server treat an HTTP PUT request with a Range header as a
- partial PUT? Note that while RFC 7233 clarified that Range headers only
- valid for GET requests, RFC 9110 (which obsoletes RFC 7233) now allows
- partial puts. [true]
+ Should the server treat an HTTP PUT request with a Content-Range header
+ as a partial PUT? 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]
</property>
<property name="directoryRedirectStatusCode">
When a directory redirect (trailing slash missing) is made, use this as
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
