Changelog for
libmicrohttpd12-1.0.1-117.5.i586.rpm :
* Sat Feb 24 2024 Andreas Stieger
- libmicrohttpd 1.0.1:
* build system fixes
* Mon Feb 05 2024 Andreas Stieger - libmicrohttpd 1.0.0:
* first stable release
* Client request parsing was rewritten to RFC 9910 and RFC 9112
* Support for strict and lenient specification enforcement
* Digest Auth was reworked, improved support for RFC 7617
* Improved functionality in multi-threading environment, especially with external sockets polling modes.
* Reworked Basic Auth, adding new convenient API functions.
* Re-implemented GnuTLS initialisation. Now supported libmicrohttpd-specific system-wide configuration, as well as generic GnuTLS system-wide configuration. Application may adjust settings based on system configuration instead of specifying its own full configuration.
* Wed May 31 2023 Andreas Stieger - libmicrohttpd 0.9.77:
* improvements for Digest and Basic authorizations
* fix efficiency for TLS upgraded connections
* fix processing of folded headers in requests
* fix functionality with blocking sockets- update upstream signing key
* Tue Feb 28 2023 Andreas Stieger - libmicrohttpd 0.9.76
* CVE-2023-27371: Fix potential DoS vector in MHD_PostProcessor (boo#1208745)
* Mon Dec 27 2021 Andreas Stieger - libmicrohttpd 0.9.75:
* fixes for where \"monotonic\" clock may jump back
* Mon Dec 20 2021 Andreas Stieger - libmicrohttpd 0.9.74:
* new experimental implementation of WebSockets disabled by default
* improved compliance with the RFC HTTP specifications
* new implementation of reply header forming
* new implementation of request chunked encoding parsing
* new automatic error replies
* Keep-alive header is omitted by default for HTTP/1.1 connections. Use of header can be enforced by response flag.
* Chunked encoding is used for HTTP/1.1 non-keep-alive connections for responses with unknown size. Previously MHD used \"indication of the end of the response by closing connection\" in such cases, however it is not correct for HTTP/1.1 connections as per HTTP RFC.
* As required by HTTP RFC, use HTTP/1.1 version instead of HTTP/1.0 in reply headers when client is HTTP/1.0 . HTTP/1.0 version can be enforced by response flag.
* User response headers are used in replies in the same order as was added by application.
* Allowed tab characters in response header values.
* All custom \"Connection:\" response headers are automatically combined into single \"Connection:\" header.
* \"keep-alive\" token silently dropped from custom \"Connection:\" response header. \"Keep-alive\" cannot be enforced and used automatically if possible.
* Allow tab character in custom response header value.
* Disallow space character in custom response header value.
* Do not allow responses with 1xx codes for HTTP/1.0 requests.
* Detected and reported incorrect \"Upgrade\" responses.
* Tue May 18 2021 Andreas Stieger - libmicrohttpd 0.9.73:
* new function for vector-backed responses
* compatibility with autoconf 2.70+
* Implement ALPN support
* Tue Dec 29 2020 Andreas Stieger - libmicrohttpd 0.9.72:
* improved performance with stay-alive HTTP and HTTPS connections
* bug fixes- remove deprecated texinfo macros
* Sat Jul 04 2020 Andreas Stieger - libmicrohttpd 0.9.71:
* Fix buffer overflow issue in URL parser [boo#1173718]
* Fixed PostProcessor bug
* Documentation and example fixes
* Sun Feb 09 2020 Martin Hauke - Update to 0.9.70:
* Fixed 100-continue handling for PATCH method
* Fixed FTBFS from wrong #endif position for certain builds
* Fixed connection overflow issue when combining MHD_USE_NO_LISTEN_SOCKET with MHD_USE_THREAD_PER_CONNECTION
* Updated m4 script to fix FTBFS when using - Werror=unused-but-set-parameter
* Adding fix for urlencoding of keys without values in post-processor logic.
* Adding patch from Ethan Tuttle with test case for urlencoding in post-processor for keys without values.
