I forwarded the email to Jitsi mailing list and they are going to take a
look. At first sight, seems indeed a bug there.
Cheers,
Daniel
On 3/27/11 1:32 PM, IƱaki Baz Castillo wrote:
2011/3/27 Daniel-Constantin
Mierla<miconda(a)gmail.com>om>:
Presence configuration with XCAP:
*
http://asipto.com/u/sp It's being a hard task for me to report a bug in
Jitsi tracker or
subscribing to the maillist, so I report a bug just here (hopefully
authors read this maillist):
When Jitsi uploads the resource-list (XCAP PUT) it set a wrong Content-Type:
-----------------------------------------
PUT /resource-lists/users/sip:alice@example.org/index HTTP/1.1'
Connection: close'
Content-Length: 231'
Content-Type: application/xcap-caps+xml'
Content-Encoding: UTF-8'
Host: example.org:800'
User-Agent: Apache-HttpClient/4.0.1 (java 1.5)'
Expect: 100-Continue'
<?xml version="1.0" encoding="UTF-8"
standalone="no"?><resource-lists
xmlns="urn:ietf:params:xml:ns:resource-lists"><list
name="RootGroup"><entry
uri="sip:bob@example.org"/></list></resource-lists>
---------------------------------------
Why is it using "Content-Type: application/xcap-caps+xml"??? Such mime
type is just for discovering XCAP Server Capabilities!:
http://tools.ietf.org/html/rfc4825#section-12
The mime type for a resource-lists document must be
application/resource-lists+xml:
http://tools.ietf.org/html/rfc4826#section-3.4.2
Regards.
--
Daniel-Constantin Mierla
http://www.asipto.com