...
Jira Ticket: https://issues.apache.org/jira/browse/TS-1728
HTTP
...
transaction buffering control
To avoid potential memory consumption issues, transactions can now be set to be throttled when their buffer usage exceeds a bound, and released when it becomes lower. This can also be used as a rough bandwidth throttle per transaction, as limiting the buffer space will throttle origin server connection bandwidth if the client or cache is unable to keep up. This can be set per transaction via the plugin APIBeing able to throttle HTTP streams can be a valuable function for reducing bandwidth waste. TBD more details, Alan.
The following configurations have been added to control this feature (the default values are shown):
| Code Block |
|---|
CONFIG proxy.config.http.flow_control.enabled INT 0 CONFIG proxy.config.http.flow_control.high_water INT 065536 CONFIG proxy.config.http.flow_control.low_water INT 065536 |
Jira Ticket: https://issues.apache.org/jira/browse/TS-1496
...