> v0 cookies, the spec says > > /NAME/=/VALUE/ > This string is a sequence of characters excluding semi-colon, comma > and white space. If there is a need to place such data in the name > or value, some encoding method such as URL style %XX encoding is > recommended, though no encoding is defined or required. > > the problem was that encoding wasn't defined nor required. so when we > followed the spec, and added %XX encoding, TCK tests failed.
Does splitting at the first = fail the TCK tests?
signature.asc
Description: OpenPGP digital signature
