The atom publishing protocol client implementation for Tomboy (http://flukkost.nu/blog/tomboyblogposter/, https://code.launchpad.net/tomboy-blogposter) submits an incomplete Content-Type (just "application/atom+xml" instead of "application/atom+xml;type:entry"). Can this media type be considered acceptable as well?

CommentFileSizeAuthor
atompub-accept-plain-atom-xml-type.patch1.34 KBmlncn

Comments

stefan freudenberg’s picture

stefan freudenberg commented

The change to AtompubCollection::post looks good. A similar change should be made to AtompubDocument::put. The AtompubUnsupportedMediaType exception should not be changed like suggested.

stefan freudenberg’s picture

stefan freudenberg commented
Status: Needs review » Fixed

I have applied a modified version of the patch. After further reading of the Atom documentation I think a request should be filed against the tomboy plugin. The mime type for Atom requires using the type parameter to distinguish between feeds and individual entries.

stefan freudenberg’s picture

stefan freudenberg commented

Apparently it is ok to only provide "application/atom+xml" as the content type: http://www.atomenabled.org/developers/protocol/atom-protocol-spec.php#rf...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Improved wording