Skip to content

Commit f8276a9

Browse files
committed
removed verify_token
1 parent 30a1361 commit f8276a9

File tree

2 files changed

+3
-55
lines changed

2 files changed

+3
-55
lines changed

pubsubhubbub-core-0.3.html

Lines changed: 2 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
22
<html lang="en"><head><title>Draft: PubSubHubbub Core 0.3 -- Working Draft</title>
3-
<meta http-equiv="Expires" content="Tue, 09 Feb 2010 05:18:45 +0000">
43
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
54
<meta name="description" content="PubSubHubbub Core 0.3 -- Working Draft">
6-
<meta name="generator" content="xml2rfc v1.33 (http://xml.resource.org/)">
5+
<meta name="generator" content="xml2rfc v1.36 (http://xml.resource.org/)">
76
<style type='text/css'><!--
87
body {
98
font-family: verdana, charcoal, helvetica, arial, sans-serif;
@@ -211,8 +210,6 @@ <h3>Table of Contents</h3>
211210
Best Practices<br />
212211
&nbsp;&nbsp;&nbsp;&nbsp;<a href="#hubbestpractices">8.1.</a>&nbsp;
213212
For Hubs<br />
214-
&nbsp;&nbsp;&nbsp;&nbsp;<a href="#subbestpractices">8.2.</a>&nbsp;
215-
For Subscribers<br />
216213
<a href="#rfc.references1">9.</a>&nbsp;
217214
References<br />
218215
<a href="#anchor11">Appendix&nbsp;A.</a>&nbsp;
@@ -497,13 +494,6 @@ <h3>Table of Contents</h3>
497494
the request was made over <a class='info' href='#RFC2818'>HTTPS<span> (</span><span class='info'>Rescorla, E., &ldquo;HTTP Over TLS,&rdquo; May&nbsp;2000.</span><span>)</span></a> [RFC2818]. This
498495
parameter MUST be less than 200 bytes in length.
499496
</dd>
500-
<dt>hub.verify_token</dt>
501-
<dd>OPTIONAL. A subscriber-provided
502-
opaque token that will be echoed back in the verification request to
503-
assist the subscriber in identifying which subscription request is
504-
being verified. If this is not included, no token will be included
505-
in the verification request.
506-
</dd>
507497
</dl></blockquote>
508498

509499
<p>The following keywords are supported for hub.verify:
@@ -634,11 +624,6 @@ <h3>Table of Contents</h3>
634624
present for unsubscribe requests and MUST be ignored by subscribers
635625
during unsubscription.
636626
</dd>
637-
<dt>hub.verify_token</dt>
638-
<dd>OPTIONAL. The subscriber-provided
639-
opaque token from the corresponding subscription request, if one was
640-
provided.
641-
</dd>
642627
</dl></blockquote>
643628

644629
<a name="anchor8"></a><br /><hr />
@@ -647,7 +632,7 @@ <h3>Table of Contents</h3>
647632
Verification Details</h3>
648633

649634
<p>The subscriber MUST confirm that the <tt>hub.topic
650-
</tt> and <tt>hub.verify_token</tt> correspond
635+
</tt> corresponds
651636
to a pending subscription or unsubscription that it wishes to carry
652637
out. If so, the subscriber MUST respond with an HTTP success (2xx)
653638
code with a response body equal to the <tt>hub.challenge</tt> parameter. If the subscriber does
@@ -960,17 +945,6 @@ <h3>Table of Contents</h3>
960945
an important issue that hubs should address instead of putting
961946
the burden on publishers and subscribers.
962947
</p>
963-
<a name="subbestpractices"></a><br /><hr />
964-
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
965-
<a name="rfc.section.8.2"></a><h3>8.2.&nbsp;
966-
For Subscribers</h3>
967-
968-
<p>The <tt>hub.verify_token</tt> parameter in
969-
subscription requests enables subscribers to verify the identity and
970-
intent of the hub making the verification request. Subscribers should
971-
use the token to retrieve internal state to ensure the subscription
972-
request outcome is what they intended.
973-
</p>
974948
<a name="rfc.references1"></a><br /><hr />
975949
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
976950
<h3>9.&nbsp;References</h3>
@@ -1039,13 +1013,4 @@ <h3>Authors' Addresses</h3>
10391013
<tr><td class="author" align="right">Email:&nbsp;</td>
10401014
<td class="author-text"><a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</a></td></tr>
10411015
</table>
1042-
<script type="text/javascript">
1043-
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
1044-
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
1045-
</script>
1046-
<script type="text/javascript">
1047-
try {
1048-
var pageTracker = _gat._getTracker("UA-7156573-1");
1049-
pageTracker._trackPageview();
1050-
} catch(err) {}</script>
10511016
</body></html>

pubsubhubbub-core-0.3.xml

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -339,12 +339,6 @@
339339
the request was made over <xref target="RFC2818">HTTPS</xref>. This
340340
parameter MUST be less than 200 bytes in length.</t>
341341

342-
<t hangText="hub.verify_token">OPTIONAL. A subscriber-provided
343-
opaque token that will be echoed back in the verification request to
344-
assist the subscriber in identifying which subscription request is
345-
being verified. If this is not included, no token will be included
346-
in the verification request.</t>
347-
348342
</list></t>
349343

350344
<t>The following keywords are supported for hub.verify:</t>
@@ -467,16 +461,12 @@
467461
present for unsubscribe requests and MUST be ignored by subscribers
468462
during unsubscription.</t>
469463

470-
<t hangText="hub.verify_token">OPTIONAL. The subscriber-provided
471-
opaque token from the corresponding subscription request, if one was
472-
provided.</t>
473-
474464
</list></t>
475465

476466
<section title="Verification Details">
477467

478468
<t>The subscriber MUST confirm that the <spanx style="verb">hub.topic
479-
</spanx> and <spanx style="verb">hub.verify_token</spanx> correspond
469+
</spanx> corresponds
480470
to a pending subscription or unsubscription that it wishes to carry
481471
out. If so, the subscriber MUST respond with an HTTP success (2xx)
482472
code with a response body equal to the <spanx
@@ -811,13 +801,6 @@ User-Agent: MyHub (+http://hub.example.com; 26 subscribers)
811801
the burden on publishers and subscribers.</t>
812802
</section>
813803

814-
<section anchor="subbestpractices" title="For Subscribers">
815-
<t>The <spanx style="verb">hub.verify_token</spanx> parameter in
816-
subscription requests enables subscribers to verify the identity and
817-
intent of the hub making the verification request. Subscribers should
818-
use the token to retrieve internal state to ensure the subscription
819-
request outcome is what they intended.</t>
820-
</section>
821804
</section>
822805
</middle>
823806

0 commit comments

Comments
 (0)