5.0.2

What's Changed

Possible breaking change

Due to security reasons, header name and value validation was enabled by default. If you face issues with some clients that send non-compliant headers, revert this change by setting the following system properties:

• org.glassfish.grizzly.http.STRICT_HEADER_NAME_VALIDATION_RFC_9110=false
• org.glassfish.grizzly.http.STRICT_HEADER_VALUE_VALIDATION_RFC_9110=false

However, this is highly discouraged as it opens options for vulnerability exploits.

Changes

• Strict header name and value validation by default by @OndroMih in #2296
• Implement HTTP 103 Early Hints (RFC 8297) interim responses by @BalusC in #2298
• Fixed "Keep-alive connection processing breaks with SameThreadIOStrategy after suspend/resume" by @carryel in #2299

New Contributors

• @BalusC made their first contribution in #2298

Full Changelog: 5.0.1...5.0.2