-
Bug
-
Resolution: Done
-
Major
-
7.1.4.GA
-
None
JBoss does not properly handle requests with range headers for files greater than 10 mb in size. For example:
curl -v -H "Range: bytes=999999-999999" localhost:8080/app/largefile
...
< HTTP/1.1 206 Partial Content
< X-Powered-By: Undertow/1
< Server: JBoss-EAP/7
< Accept-Ranges: bytes
< Date: Mon, 26 Nov 2018 20:13:59 GMT
< Connection: keep-alive
< Last-Modified: Mon, 26 Nov 2018 20:13:19 GMT
< Content-Range: bytes 999999-999999/10504296
< Content-Type: text/html
< Content-Length: 1
<
* Excess found in a non pipelined read: excess = 16086, size = 1, maxdownload = 1, bytecount = 0
* Connection #0 to host localhost left intact
So with the above, JBoss indicates a content length of 1 as we'd expect, but the response data sent back to the client actually appears to be the first 16 kb of the file instead of the requested range.
- clones
-
JBEAP-15919 [GSS](7.2.z) UNDERTOW-1444 - Range headers do not seem to be handled correctly for files larger than 10 mb
- Closed
- incorporates
-
UNDERTOW-1444 Caching resource manager does not handle range requests if file is too large to fit in cache
- Resolved
- is incorporated by
-
JBEAP-15370 (7.1.z) Upgrade undertow from 1.4.18.SP9 to 1.4.18.SP11
- Closed
- links to