The assumption here is that SET-COOKIE header returned to Knox will always have spaces between the fields
Which is not the case when CM returns the SET-COOKIE header
Which breaks the Knox logic.
Examples in RFC https://tools.ietf.org/html/rfc6265#section-2.2 have whitespace but they do not specify format. Since CM uses it and it was working up until now Knox should be fixed to support it.