Hello, According to the RFC 4825 (Para. 8.2.2.), the server MUST return a 409 response code:
8.2.2. Verifying Document Content If the PUT request is for a document (the request URI had no node selector separator), the content of the request body has to be a well-formed XML document. If it is not, the server MUST reject the request with a 409 response code. That response SHOULD include a detailed conflict report including the <not-well-formed> element. If the document is well-formed but not UTF-8 encoded, the server MUST reject the request with a 409 response code. That response SHOULD include a detailed conflict report including the <not-utf-8> element. If the MIME type in the Content-Type header field of the request is not equal to the MIME type defined for the application usage, the server MUST reject the request with a 415. Regards, Laurent Etiemble. Need an IMS Client ? Try out the Mercuro IMS Client Full support for OMA/3GPP XCAP/XDMS More info at: http://www.mercuro.net/ 2010/1/18 Iñaki Baz Castillo <[email protected]>: > Hi, in case a XCAP clients upload to the server a syntactically wrong XML > (i.e: ">" missing), which should be the response fro the XCAP server? > > a) 400 Bad Request > b) 409 Conflict > > IMHO it's 400, but I would like to know more opinnions. > > Thanks. > > > -- > Iñaki Baz Castillo <[email protected]> > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
