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 36cf8f7c16 update terms about partial PUT - a PUT with Content-Range
Header (#795)
36cf8f7c16 is described below
commit 36cf8f7c160d66b6474b30584e3760803d53d4d0
Author: Chenjp <ch...@msn.com>
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
---
webapps/docs/default-servlet.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/webapps/docs/default-servlet.xml b/webapps/docs/default-servlet.xml
index 3e98eaa7da..dcdd743ef0 100644
--- a/webapps/docs/default-servlet.xml
+++ b/webapps/docs/default-servlet.xml
@@ -202,10 +202,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: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
