5 messages in com.googlegroups.bloggerdevRe: [bloggerDev] Content-type change?...| From | Sent On | Attachments |
|---|---|---|
| liyanage | 24 Jul 2006 06:44 | |
| Pete Hopkins ☠ | 24 Jul 2006 10:44 | |
| Marc Liyanage | 24 Jul 2006 15:11 | |
| liyanage | 25 Jul 2006 03:00 | |
| Pete Hopkins ☠ | 25 Jul 2006 13:43 |
| Subject: | Re: [bloggerDev] Content-type change? / NPE on posting |
|---|---|
| From: | Pete Hopkins ☠ (phop...@google.com) |
| Date: | 07/24/2006 10:44:25 AM |
| List: | com.googlegroups.bloggerdev |
On 7/24/06, liyanage <liya...@gmail.com> wrote:
I have two issues, the first one led to the second one.
1.) Our web based service/application can no longer post to Blogger.com using the Atom API. We are posting to the /feeds/<n>/posts/full URL. This used to work and was tested extensively. Now if I try it, I get
Content-Type must be 'application/atom+xml', not 'application/x.atom+xml;charset=iso-8859-1
We have two posting modes, one uses application/x.atom+xml and the other one uses application/xml.
So my first question is, did this change recently? What is the correct content-type?
The /feed/... URLs are from Blogger's experimental Atom 1.0/Gdata support.
application/atom+xml is the correct content type.
2.) When I tried to submit with the suggested content type application/atom+xml, I get the NPE below. My second question is, are we doing something wrong?
This appears to be a bug in one of our exceptional case handling bits. What are you sending as the Authorization header on the request? (you may omit any password part in your response)
I just tried it again with the https and /atom/<n> URL, and that seems to work, but our autodiscovery code currently picks up the other <link> service.post option, and existing customers might have that stored in their profiles too, so I'd like to know how to get that to work again.
We tried to be backwards-compatible when including the Atom 1.0 feeds. They should come later in the <head> than the Atom 0.3 links. If you need to distinguish them (to avoid them, perhaps) then look for the "(Atom 1.0)" string in the title attribute.
We will soon be making a transition from Atom 0.3 to Atom 1.0, however, so getting things to work with Atom 1.0 is worthwhile.
-- Pete