Description
When using the 'addValue:forHTTPHeaderField', it incrementally appends the key-value using a comma.
Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list
// https://tools.ietf.org/html/rfc2616#page-32
May be we should use 'setValue: forHTTPHeaderField', which avoids the issue of cookies with comma delimiter, instead semi-colon delimiter.
Related GH issue: https://github.com/couchbase/couchbase-lite-ios/issues/2828
Validate fix using proxy app?
Attachments
Issue Links
- is cloned by
-
CBL-2184 [Backport] Add cookie using setValue instead of addValue
-
- Closed
-