Julien, Thanks, that did the trick!
Would it make sense for the pshb spec to specify that hub's treat topic url's as case-insensitive? Actually just looked at the URI spec (RFC 3986) and it seems that resources after the domain are technically case-insensitive but really left up to the server to decide. So technically those two url's (TechCrunch vs Techcrunch) could serve up different resources, though I wonder how common that actually is in practice, particularly for a feed xml. Alternatively, would it make sense for the hub to check if there is actually a publisher registered send pings for that topic url and respond with failure to a client subscription attempt for such a topic url that's not registered? It looks like currently the hub successfully verifies a subscription to any random url http://www.google.com/blah/blah/blah for example. Is there a reason this is allowed by the protocol currently? Thanks! Franco On Thursday, November 21, 2013 2:09:17 AM UTC-8, Franco wrote: > > I am not receiving notifications for > http://feeds.feedburner.com/TechCrunch. My client has successfully > subscribed and I verified my callback address is subscribed for this topic > at https://pubsubhubbub.appspot.com/subscribe > > I am successfully receiving notifications for several other subscriptions > including feedburner feeds. > -- --- You received this message because you are subscribed to the Google Groups "Pubsubhubbub" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
