just50415 / android-rcs-ims-stack

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

Client uses unquoted etags in XCAP operations #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Configure client with xcap support.
2. Ensure xcap server supports org.openmobilealliance.xcap-directory, and has a 
document (any document) provisioned in the user's resource-lists tree.
3. Client does an XCAP GET operation with an unquoted If-match header field 
value.

What is the expected output? What do you see instead?

From the XCAP GET:
GET 
/resource-lists/users/sip%3AAndroid1%40example.com/index/~~/resource-lists/list%
5B@name=%22rcs%22%5D HTTP/1.1
Host: example.com:80
User-Agent: OrangeLabs-RCS-client 2.2.0
X-3GPP-Intended-Identity: Android1
If-match: DGS9Db3adCY=
Content-Length: 0

The If-match header field value is malformed; it should read as follows (see 
RFC 2616 Sec 3.11):

GET 
/resource-lists/users/sip%3AAndroid1%40example.com/index/~~/resource-lists/list%
5B@name=%22rcs%22%5D HTTP/1.1
Host: example.com:80
User-Agent: OrangeLabs-RCS-client 2.2.0
X-3GPP-Intended-Identity: Android1
If-match: "DGS9Db3adCY="
Content-Length: 0

What version of the product are you using? On what operating system?

2.2.0, emulator on OS X 10.6.6

Please provide any additional information below.

Original issue reported on code.google.com by docfara...@gmail.com on 24 Feb 2011 at 4:30

GoogleCodeExporter commented 8 years ago
You are right. This will be corrected in the next release. Thanks.

Original comment by jmauffret@gmail.com on 15 Mar 2011 at 3:41

GoogleCodeExporter commented 8 years ago

Original comment by jmauffret@gmail.com on 28 Mar 2011 at 6:40