Add a way to set custom cookie parsers to be compliant with rfc6265 section 4.1.1
java.net.HttpCookie::parse still follows rfc2965: https://docs.oracle.com/javase/8/docs/api/java/net/HttpCookie.html#parse-java.lang.String- That has been obsoleted from rfc6265: https://datatracker.ietf.org/doc/html/rfc6265 That in section 4.1.1 states the following:
Each cookie begins with a name-value-pair, followed by zero or more attribute-value pairs.
Servers SHOULD NOT send Set-Cookie headers that fail to conform to the following grammar:
So the MUST constraint from rfc2965 has been relaxed to SHOULD NOT in rfc6265
I think that taking this into account, it may also be a good idea to collapse some features between the Jetty response connector and the JDK response connector, and provide a way to customize the cookie parser.