Isn't that inadvertantly describing a GET request? In a POST request the parameters are added to the body. If you're using a wrapper HTTP client (which uses curl or something like PHP streams under the hood) it should do all this automatically.
There are exceptions - when using HMAC (Subscriber <-> Hub only) some languages don't actually apply RFC 3986 encoding by default which is absolutely necessary to ensure the data being signed is enforcing a strict encoding scheme common to all implementations across all languages. PHP is a pain in the ass this way - it misses that "~" is a reserved character when encoding which makes it non-compliant with the RFC. Paddy Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Tim Bray <[email protected]> To: [email protected] Sent: Sun, October 18, 2009 10:20:38 PM Subject: [pubsubhubbub] 7.1 New Content Notification; why request body required? Since all the publisher is sending is a couple of fields, why does it have to send a request body? For example, to hook up my own blog, all I have to send is hub.mode=publish&hub.url=http://www.tbray.org/ongoing/ongoing.atom So I'm wondering why I can't just POST an empty body to http://pubsubhubbub.appspot.com/?hub.mode=publish&hub.url=http://www.tbray.org/ongoing/ongoing.atom No content-type, no content-length, less work all around? -T
