Chenjp commented on PR #810:
URL: https://github.com/apache/tomcat/pull/810#issuecomment-2694798531
This part is semantically ambiguous, and yet undefined in RFC.
We have to make decision when edge case happen:
1. payload length is larger than content-range. (e.g. payload="0123456789",
content-range header: bytes 10-14/15)
***candidate actions***:
1.a) action 1: reject request
1.b) action 2: ensure the data boundary of the write is defined by
content-range header, discard rest part of payload.
e.g. write "01234" from the beginning index 10. // 5 bytes written
1.c) action 3: payload is fully written from the beginning index
(start-position) defined in content-range header.
e.g. write "0123456789" from the beginning index 10. // 10 bytes
written
2. payload length is smaller than content-range. (e.g. payload=01234,
content-range header: bytes 10-14/15)
***candidate actions***:
2.a) action 1: reject request
2.b) action 2: ensure the data boundary of the write is defined by
content-range header, fill with byte(0) if absent.
e.g. write "01234\0\0\0\0\0" from the beginning index 10. // 10
bytes written.
2.c) action 3: payload is fully written from the beginning index
(start-position) defined in content-range header.
e.g. write "01234" from the beginning index 10. // 5 bytes written
@rmaucher which group is better?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
