-
Bug
-
Resolution: Fixed
-
P2
-
10
-
b41
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8196648 | 11 | Chris Hegarty | P2 | Resolved | Fixed | b01 |
| JDK-8197765 | 10u-cpu | Chris Hegarty | P2 | Resolved | Fixed | master |
| JDK-8200969 | 10.0.2 | Unassigned | P2 | Resolved | Fixed | b01 |
| JDK-8196692 | 10.0.1 | Chris Hegarty | P2 | Resolved | Fixed | b04 |
It has been observed that byte buffers passed to the response subscriber may contain unprocessed data in the area between the buffer's limit and its capacity. This can happen when:
1) reading chunked HTTP/1.1 response data
2) receiving HTTP/2 data frames for several streams
It is problematic for many reasons, least of all is that the asString and buffering subscribers accumulate bytes, below a certain threshold, into given buffers ( so as to not necessarily consumer memory ). There could also be other, more serious, issues.
1) reading chunked HTTP/1.1 response data
2) receiving HTTP/2 data frames for several streams
It is problematic for many reasons, least of all is that the asString and buffering subscribers accumulate bytes, below a certain threshold, into given buffers ( so as to not necessarily consumer memory ). There could also be other, more serious, issues.
- backported by
-
JDK-8196648 Buffers given to response body subscribers should not contain unprocessed HTTP data
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-