mirror of
https://github.com/bitcoin/bitcoin.git
synced 2026-07-12 23:20:23 +02:00
3765b428d1
Libevent log category was partially removed in 39e9099da5, and this
commit extends that with the following changes:
- Stops showing libevent in the list of supported log categories in
`bitcoind -help` and `bitcoin-cli help logging` output.
- Stops returning `"libevent": false` in `logging` RPC output.
It's not good to treat libevent as a supported log category when it
can't be enabled and trying to enable it results in warnings.
There's also no need to define an unused LIBEVENT constant value and
keep more complicated logic for dealing with deprecated log categories,
so this change also simplifies code internally.
Co-authored-by: David Gumberg <davidzgumberg@gmail.com>
Co-authored-by: l0rinc <pap.lorinc@gmail.com>
726 B
726 B
HTTP: RPC / REST
The HTTP server has been rewritten from scratch to replace libevent. (#35182)
The libevent logging category has been removed. Configurations like
-debug=libevent or -debugexclude=libevent will log a deprecation warning
and be ignored. These configurations will result in an error in a future release.
Certain HTTP edge cases will observe different behavior to be more RFC-compliant:
- Stricter enforcement of maximum headers size (8192 bytes)
- Reject requests with whitespace in header field-names
- "Line Folding" is rejected (whitespace at start of a header line)
- Tolerate
%at the end of requested URLs - Multiple "Content-Length" headers with different values are rejected