> -----Original Message----- > From: Remy Gendron [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 19, 2008 1:05 PM > To: [email protected] > Subject: RFC compliance questions > > 1) APP RFC seems to indicate that a successful POST > should return an HTTP 201, while PUT should return > HTTP 200. Abdera server > (AbstractEntityCollectionAdapter.putEntry) returns > a 204. Is this OK?
See RFC 5023, Section 5: 'While specific HTTP status codes are shown in the interaction diagrams below, an AtomPub client should be prepared to handle any status code. For example, a PUT to a Member URI could result in the return of a "204 No Content" status code, which still indicates success.' Notice that whenever the 200 OK status code is referenced, it is not using RFC 2119 language (SHOULD or MUST). > 2) ProviderHelper.isValidEntry will return false for an > entry with no summary but with a content item of XML type. > The RFC says, if I read correctly, that the summary item > is not required if the entry contains a content item of > XML type. Your interpretation is correct. No summary is needed unless the content element has a "src" attribute or it Base64-encoded. Additionally, if there is no content element, no summary is required either. - Brian
