v20.71.0

• Examples are built in parallel
• Supports building with all _LIBCPP_HARDENING_MODE
• (Experimental) cached HTTP support is reverted for now, restoring fuzz builds
• h1spec and test subject is added to CI
• Disallow duplicate Host headers as per RFC9112

v20.70.0

More HTTP testing & corrections

This release adds more HTTP tests and makes some minor corrections for passing those tests:

v20.69.0

HTTP spec. compliance testing

A basic HTTP RFC9112 spec. compliance test has been added and minor changes have been made to pass all tests immediately:

This basic test catches no issues in Node.js, but it catches 2 issues in Deno (reported). The test can be found here:

https://github.com/uNetworkingAB/h1spec

In contrast, running the test on completely broken servers like mrhttp you get an obvious indication of so:

v20.68.0

Improved (restored) backwards compatibility

For some users, recent introduction of CachedApp broke seamless backwards compatibility. If you rely on uWS::App being uWS::TemplatedApp<false> and not something else (like uWS::CachedApp<false> 😉), this release fixes your build:

    typedef uWS::TemplatedApp<false> App;
    typedef uWS::TemplatedApp<true> SSLApp;

v20.67.0

• Adds removeChildApp

v20.66.0

Minor HTTP corrections

• Emit 431 on too many headers (not just too long headers)
• Don't emit 505 on fragmented request line (regression since 505 was introduced)

v20.65.0

• Always put a reason message on 1006 close events
• Template refactors needed for coming HTTP cache; it should be entirely backwards compatible for your app

v20.64.0

• uWebSockets is now 22% faster than simdutf in validating [mostly English] UTF-8.

v20.63.0

• Make use of ERR_INVALID_CLOSE_PAYLOAD to better explain such closures.
• Remove C-API as it is no longer maintained here, but rather over at the Bun repo.
• It's invalid to pass nullptr to memcpy even with 0 size according to UndefinedBehaviorSanitizer, so this is now fixed.

v20.62.0

RFC 9110 fix part trois

• DQUOTE is not a valid field name char
• "431 Request Header Fields Too Large" will be emitted more strictly
  • Reminder: you can set the environment variable UWS_HTTP_MAX_HEADERS_SIZE higher if you need to