Topic URL should be included in content notification for non-aggregated delivery

[GoogleCodeExporter]

SUMMARY:

A common ask from subscribers is to get the feed URL of the original
subscription on each content delivery. This is already in the feed, but it
would simplify a common use-case to always include a header with it. For
the aggregated case the header would be missing. The header 'X-Hub-Topic'
would be a good fit.

RELEVANT SECTION: 7

Original issue reported on code.google.com by bslatkin on 25 Sep 2009 at 11:37

[GoogleCodeExporter]

I'm leaning towards marking this one as not fix. With query string parameters 
being 
passed on to subscriber endpoints and database lookups presumably happening at 
event delivery time, it seems redundant to include the topic URL again in the 
delivery 
request. Subscribers can put whatever token they need in their callback URL to 
determine the URL of the feed that had the event (this precludes aggregated 
delivery, 
but it looks like that's going to be cut out soon).

Original comment by bslatkin on 8 Feb 2010 at 11:19

[GoogleCodeExporter]

I agree - Since query parameters (or even the callback URL itself) generally 
dictate
the keys necessary to look up information on the subscriber's end, passing the 
topic
isn't necessary.

Original comment by jrossi...@gmail.com on 1 Mar 2010 at 8:35

[GoogleCodeExporter]

you find me at 710 ellis #41 usa 94102 use caution all over

Original comment by toddleet...@gmail.com on 15 Jul 2013 at 6:44

[GoogleCodeExporter]

Since specification v0.4 the Hub's request to the subscriber "MUST include a 
Link Header with rel=hub pointing to the Hub as well as a Link Header with 
rel=self set to the topic that's being updated" (section 7. Content 
Distribution). Since the reference implementation ignores that part I have 
attached a patch that implements the missing functionality.

Original comment by sebbrueckner@gmail.com on 8 Jan 2014 at 3:52

Attachments:

• push-hub-linkheader.patch