You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the request was made over <aclass='info' href='#RFC2818'>HTTPS<span> (</span><spanclass='info'>Rescorla, E., “HTTP Over TLS,” May 2000.</span><span>)</span></a> [RFC2818]. This
498
495
parameter MUST be less than 200 bytes in length.
499
496
</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>
507
497
</dl></blockquote>
508
498
509
499
<p>The following keywords are supported for hub.verify:
@@ -634,11 +624,6 @@ <h3>Table of Contents</h3>
634
624
present for unsubscribe requests and MUST be ignored by subscribers
635
625
during unsubscription.
636
626
</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>
642
627
</dl></blockquote>
643
628
644
629
<aname="anchor8"></a><br/><hr/>
@@ -647,7 +632,7 @@ <h3>Table of Contents</h3>
647
632
Verification Details</h3>
648
633
649
634
<p>The subscriber MUST confirm that the <tt>hub.topic
650
-
</tt>and <tt>hub.verify_token</tt> correspond
635
+
</tt>corresponds
651
636
to a pending subscription or unsubscription that it wishes to carry
652
637
out. If so, the subscriber MUST respond with an HTTP success (2xx)
653
638
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>
960
945
an important issue that hubs should address instead of putting
0 commit comments