11 messages in com.googlegroups.bloggerdevRe: [bloggerDev] Re: PostNotFoundExce...| From | Sent On | Attachments |
|---|---|---|
| odacrem | 31 Mar 2006 14:49 | |
| Steve Jenson | 31 Mar 2006 15:00 | |
| odacrem | 01 Apr 2006 06:29 | |
| the.Visitor | 02 Apr 2006 09:40 | |
| nuah | 02 Apr 2006 10:31 | |
| disbelief | 02 Apr 2006 19:32 | |
| ZenGen | 03 Apr 2006 06:30 | |
| Eric Case | 03 Apr 2006 10:05 | |
| Khaled A. | 03 Apr 2006 10:15 | |
| odacrem | 03 Apr 2006 16:18 | |
| Steve Jenson | 03 Apr 2006 16:29 |
| Subject: | Re: [bloggerDev] Re: PostNotFoundException![]() |
|---|---|
| From: | Eric Case (c....@google.com) |
| Date: | 04/03/2006 10:05:36 AM |
| List: | com.googlegroups.bloggerdev |
Hi folks,
Apologies for the delay, I just chatted with SteveJ and it's sounding like he's planning to push a fix sometime today.
Thanks again for your patience, -E
On 4/3/06, ZenGen <jeff...@sxii.com> wrote:
It looks like something is definitely broken.
The wget.exe client I am using is suddenly returning a 404 error when I post to the website. This stopped working on March 31st after more than half a year of daily automated posts. Something has obviously broken.
Looks like I'm not the only one with this issue.
FYI, the wget.exe command line arguments I'm using are as follows:
wget.exe --header "Content-type: application/x.atom+xml" \ --http-user=myname \ --http-passwd=mypass \ --post-file=post-bs.xml \ --output-file=./wget-bs.log \ https://www.blogger.com/atom/17474474
If this was to happen at my company, and the admin let this problem hang around for four days with no action, someone would be demoted or fired. Of course, I don't know how severe this is, and maybe I'm not being generous enough. But this is very frustrating. I've already wasted a lot of time investigating this.
odacrem wrote:
hello,
Blogger.com has suddenly started returning a horrible error when my blog client tries to create a post with the Atom protocol. The client has been working fine for months and months and months.
Whe I try to create a post I get the following response:
Exception caught but no reason given: com.google.blogger.exceptions.PostNotFoundException
Since I suspected that my client was broken, I also tried to create an Atom Entry with curl . I got the same error:
This is what I tried to do with curl:
curl -u <username>:<password> -H 'Content-Type: application/xml' --data-binary @test2.txt https://www.blogger.com/atom/<blogid>
where the contents of test2.txt is the following (lifted directly from http://code.blogger.com/archives/atom-docs.html)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <entry xmlns="http://purl.org/atom/ns#"> <title mode="escaped" type="text/html">atom test</title> <issued>2004-04-12T06:07:20Z</issued> <generator url="http://www.yoursitesurlhere.com">Your clients name here.</generator> <content type="application/xhtml+xml" xml:lang="en-US" xml:space="preserve"> <div xmlns="http://www.w3.org/1999/xhtml"><em>Update:</em> Testing the Atom API</div> </content> </entry>
anyone know what is going on?




