The inbound Cookie header should be parsed using a semicolon separator by default

The inbound Cookie header may contain something like this:

Cookie: a=b;d=c

At the moment the JAX-RS runtime assumes by default that this a single Cookie value, with the last name/value pair recognized and the first one dropped.

It appears that browsers would more often than not collapse all the Cookies targeted at the specific endpoint into a single header.
Thus a ';' should be used by default when parsing such headers; this can always be customized...