Question
In Tizen 2.4, there appears to be a bug where multiple Set-Cookie headers are being incorrectly merged into a single cookie.
For example, when sending the following headers (as shown in the MDN example):
Set-Cookie: name=value
Set-Cookie: name2=value2
The Tizen 2.4 platform (specifically on SSSP 4 TV) incorrectly combines these into a single cookie, rather than maintaining them as separate cookies. This behavior differs from standard HTTP cookie handling.
Answer
Problem Understanding
The issue occurs when a server sends multiple Set-Cookie headers in a response. While standard HTTP implementations would process these as separate cookies, Tizen 2.4 incorrectly merges them into a single cookie value. This affects web applications running on Tizen 2.4 devices, particularly Samsung Smart TVs (SSSP 4 TV model).
Solution Methods
-
Test with different cookie formats: As suggested in the answers, try various cookie combinations to confirm the behavior:
Set-Cookie: a=apple; expires=Wed, 09 May 2018 12:30:00 GMT Set-Cookie: b=ball -
Report the bug: Since this appears to be a platform-specific issue, you should:
- File a bug report on the Tizen bug tracker
- Include detailed reproduction steps and examples
- Share the bug report link in this thread for tracking
-
Workaround options:
- Consider using a single cookie with multiple values if possible
- Implement cookie handling in JavaScript as an alternative
Code Examples
Example of testing different cookie formats:
HTTP/1.1 200 OK
Content-Type: text/html
Set-Cookie: test1=value1
Set-Cookie: test2=value2; Expires=Wed, 09 May 2018 12:30:00 GMT
Additional Tips
- This issue appears specific to Tizen 2.4 and may not affect newer versions
- When reporting bugs, include:
- Exact Tizen version
- Device model
- Complete reproduction steps
- Expected vs actual behavior
- Monitor the bug report for updates and potential fixes
