I see, I thought valid-address-data referred exclusively to ADR fields.
On Sat, Aug 29, 2015 at 06:56:21AM -0700, Rob N wrote:
Thanks; I didn’t look closely at that.
The HTTP response code looks like a bug; I’m fairly sure it should be 412 (Precondition Failed). I’ll check this with our backend engineers.
Considering the response body:<D:error xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:carddav"> <C:valid-address-data/> </D:error>
This is unambiguous per RFC 6352 section 184.108.40.206.
(CARDDAV:valid-address-data): The resource submitted in the PUT request, or targeted by a COPY or MOVE request, MUST be valid data for the media type being specified (i.e., MUST contain valid vCard data).
A vCard that does not have an FN field is not a valid vCard.
Reply to this email directly or view it on GitHub: