biddyweb / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
2 stars 1 forks source link

Content-Type capital T in cpim message not supported. #39

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. A initiates IM session to B. SIP level is OK. SIP session established.
2. B responds via MSRP with cpim message containing Content-Type header (note 
capital T).
3. A party's client does not process the message correctly and therefore does 
not display the message to user A

What is the expected output? What do you see instead?
Expected would be to see the message.

What version of the product are you using? On what operating system?
2.3.4, checked also on older versions, same result. Android 2.3.4 & 2.3.3.

Please provide any additional information below.
N/A

Original issue reported on code.google.com by pkurp...@gmail.com on 3 Dec 2011 at 11:05

GoogleCodeExporter commented 9 years ago
In the RFC3862 says that the content type header has the following syntax 
"Content-type": no capital letter.

Original comment by jmauffret@gmail.com on 6 Dec 2011 at 10:47

GoogleCodeExporter commented 9 years ago
However in section 2.4. Message Content of the same RFC one can read T with 
capital letter...

Original comment by pkurp...@gmail.com on 6 Dec 2011 at 10:54

GoogleCodeExporter commented 9 years ago
And in chapter 5.1 it's another syntax ;-)I propose to be compliant in both 
cases in the code

Original comment by jmauffret@gmail.com on 6 Dec 2011 at 11:03

GoogleCodeExporter commented 9 years ago
Exactly, supporting both: lower and uppercase was my initial suggestion ;-) 
RFC 3862 seems not consistent within this area.

Original comment by pkurp...@gmail.com on 6 Dec 2011 at 11:08

GoogleCodeExporter commented 9 years ago
Ok to support both syntax. Available in next sprint.

Original comment by jmauffret@gmail.com on 7 Dec 2011 at 10:00