v2.1.0

Important note regarding Response Size Limiting

The default value for --max-size was previous set to 5120 (5KB). However, chunked encoding responses bypassed size restrictions, and only content-length type responses had response size limits enforced.

This issue has been fixed. To avoid unexpected failures, and to preserve backwards compatibility in this regard, --max-size now defaults to 0 (no size limit).

To restore the previous default, as well as enforcing response size limits on content-type responses, simply pass --max-size=5120 at startup.

Changes

• Support audio/* with --allow-content-audio flag (similar to how video is handled)
• Additional metrics datapoints when using --metrics
• Support only go 1.13, due to use of new error wrapping semantics
• Improve client connection early abort handling
• Improve max response side handling -- only read MaxSize KB from any upstream server. Note: This may result in partial responses to clients for chunked encoding requests that are longer than MaxSize, as there is no way to signal the client other than closing the connection.
• Change default of --max-size to 0, as previously chunked encoding responses bypassed size restrictions (only content-length was previously enforced). To avoid unexpected failures (preserve backwards compatibility in this regard), set max-size to 0 by default moving forward. Previous default was 5mb (use --max-size=5120 to set to previous default).