Hi,

TypePad's PuSH hub is running the version that was implemented before
PubSubHubbub spec 0.2 was out -- In 0.1 callback URL should not
contain any query parameters.
http://code.google.com/p/pubsubhubbub/source/browse/trunk/pubsubhubbub-core-0.1.xml?spec=svn235&r=176#318

We have a plan to upgrade our hub in the near future but for now you
should use path_info-like mechanism i.e. /api/sub.php/1234 to append
additional parameters. Sorry for the inconvenience.

--
Tatsuhiko Miyagawa
Software Engineer, Six Apart

On Mar 16, 2:27 pm, Pádraic Brady <[email protected]> wrote:
> Doesn't Typepad have a support system you can report this to? Look's like the 
> appended query string triggered something to normalise the URI - it's 
> certainly not functioning correctly per the specification so the problem is 
> on their end.
>
> Paddy
>
>  Pádraic Brady
>
> http://blog.astrumfutura.comhttp://www.survivethedeepend.com
> OpenID Europe Foundation Irish Representative
>
> ________________________________
> From: vivpuri <[email protected]>
> To: Pubsubhubbub <[email protected]>
> Sent: Tue, March 16, 2010 7:39:11 PM
> Subject: [pubsubhubbub] PubSubHubbub sub issue on Typepad
>
> I was working on subscribing to feeds from Typepad and came across an
> issue where the hub is:
>
> http://hubbub.api.typepad.com/
>
> Basically when i send in a request for sub with hub.callback of the
> type:http://example.com/api/sub?id=1234
>
> For that sub request, Typepad responds with something like:
>
> http://example.com/api/sub%3Fid%1234.php?hub.verify_token=......................
>
> Since script sub%3Fid%1234.php does not really existing, verification
> ends up nowhere. I guess Brad might have worked with Typepad on their
> integration. Any idea if he can get Typepad team to get this fixed or
> verify this is a real issue.
>
> Thank you
> Vivek Puri

Reply via email to