Sourced from bandit's changelog.
1.6.7 (30 Jan 2025)
Changes
- Consider timeouts when reading HTTP/1 headers as a connection error and not an HTTP error
- Enhance logging for WebSocket deflation errors
1.6.6 (25 Jan 2025)
Fixes
- Consider closures during HTTP/1 header reading as a socket error to silence them by default via
log_client_closuresconfig flag- Send
connection: closewhen closing connection on error per RFC9112§9.6Enhancements
- Add experimental opt-in trace logging to help diagnose hard to reproduce errors
- Move CI to 1.18 & improve tests (#459, #461, thanks
@grzuy!)1.6.5 (15 Jan 2025)
Fixes
- Fix regression introduced in 1.6.1 where we would not send headers set by the Plug during WebSocket upgrades (#458)
Enhancements
- Properly normalize Erlang errors before emitting telemetry and logged crash_reason (#455, thanks
@grzuy!)1.6.4 (11 Jan 2025)
Fixes
- Fix error in socket setup error handling introduced in 1.6.2 (thanks
@danielspofford!)1.6.3 (8 Jan 2025)
Fixes
- Always close HTTP/1 connection in any case where an error comes out of the plug (#452, thanks
@zookzook!)- Fix dialyzer warning introduced by Thousand Island 1.3.9
1.6.2 (4 Jan 2025)
Enhancements
... (truncated)
5879549
Version bump to 1.6.72f55abc
Include details of websocket deflation error8f257f1
Consider HTTP/1 header read timeouts as connection errors575c396
Version bump to 1.6.6137ff68
Fixup dialyzer warning under 1.189e6ba26
Don't credo test filesf62faab
Version bump CI to 1.18/27a5fcb83
Minor typo5adc828
Trace tooling (#453)bc0a4fd
Use an apply when inducing runtime crashes in order to fool the
increasingly ...