Skip to content

allow topic URL in places other than the Link header #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
julien51 merged 1 commit into from
May 19, 2015
Merged

allow topic URL in places other than the Link header #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pubsubhubbub-core-0.4.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@
<t>Hubs MUST ignore additional request parameters they do not understand.</t>
<t>Hubs MUST allow subscribers to re-request subscriptions that are already activated. Each subsequent request to a hub to subscribe or unsubscribe MUST override the previous subscription state for a specific topic URL and callback URL combination once the action is verified. Any failures to confirm the subscription action MUST leave the subscription state unchanged. This is required so subscribers can renew their subscriptions before the lease seconds period is over without any interruption.</t>
<section title="Subscription Parameter Details">
<t>The topic and callback URLs MAY use <xref target="RFC2616">HTTP</xref> or <xref target="RFC2818">HTTPS</xref> schemes. The topic URL MUST be the one advertised by the publisher in a Self Link Header during the discovery phase. (See <xref target="discovery"></xref>). Hubs MAY refuse subscriptions if the topic URL does not correspond to the one advertised by the publisher. The topic URL can otherwise be free-form following <xref target="RFC3986">the URI spec</xref>. Hubs MUST always decode non-reserved characters for these URL parameters; see section 2.4 on <spanx style="emph">"When to Encode or Decode"</spanx> in <xref target="RFC3986">the URI spec</xref>.</t>
<t>The topic and callback URLs MAY use <xref target="RFC2616">HTTP</xref> or <xref target="RFC2818">HTTPS</xref> schemes. The topic URL MUST be the one advertised by the publisher during the discovery phase. (See <xref target="discovery"></xref>). Hubs MAY refuse subscriptions if the topic URL does not correspond to the one advertised by the publisher. The topic URL can otherwise be free-form following <xref target="RFC3986">the URI spec</xref>. Hubs MUST always decode non-reserved characters for these URL parameters; see section 2.4 on <spanx style="emph">"When to Encode or Decode"</spanx> in <xref target="RFC3986">the URI spec</xref>.</t>
<t>The callback URL MAY contain arbitrary query string parameters (e.g., <spanx style="verb">?foo=bar&amp;red=fish</spanx>). Hubs MUST preserve the query string during subscription verification by appending new parameters to the end of the list using the <spanx style="verb">&amp;</spanx> (ampersand) character to join. Existing parameters with names that overlap with those used by verification requests will not be overwritten. For event notification, the callback URL will be POSTed to including any query-string parameters in the URL portion of the request, not as POST body parameters.</t>
</section>
<section title="Subscription Response Details">
Expand Down