Chris, I checked the logs on the app and I only see a single request to that subscribe URL (it appears to be a GET sent from Firefox/Gentoo/x86_64).
I just used that subscription URL to successfully add (and remove :)) a subscription to the TechCrunch FeedBurner feed (http://feeds.feedburner.com/TechCrunch) with that XMPP account. I used the top form on this page: http://pubsubhubbub.appspot.com/subscribe . Could it have been a temporary failure for outgoing requests in AppEngine? Here are the values that tested successfully: Callback: (the subscriber URL) http://pubsubhubbub-xmpp.appspot.com/subscribe/[email protected] Topic: (the feed URL) http://feeds.feedburner.com/TechCrunch Verify type: Sync Mode: Subscribe Verify token: (can be anything) Matt. On Wed, Sep 30, 2009 at 11:30 AM, Brett Slatkin <[email protected]> wrote: > +matthew > > Matt, Any ideas on this one? > > On Wed, Sep 30, 2009 at 10:20 AM, c.cobb <[email protected]> wrote: >> >> That did it. Thank you for the quick reply. I tried that earlier, but >> obviously had something else wrong at the time. Then, when actually >> *reading* the 0.2 spec, saw it wanted a "response body," and >> ass*u*me'd that meant an HTML body. >> >> Next question: I'm still seeing this same error message when I try to >> subscribe an XMPP client to the feed: >> http://pubsubhubbub-xmpp.appspot.com/subscribe/[email protected] >> ...this URI was generated by the http://pubsubhubbub-xmpp.appspot.com/ >> form. The xmpp user is a friend of <[email protected]> >> and, at the time I try to subscribe, the user is online. Not sure how >> to start debugging this one. >> >> This is the part I'm really interested in. I've been wanting to have a >> Jabber-enabled server since first playing around with Jabber libs >> maybe 8 or 9 years ago, and I'm hoping that PuSH w/XMPP can make this >> simple. This is great stuff. Thanks. >> >
