On Fri, Jul 30, 2010 at 6:43 AM, Cole <[email protected]> wrote: > ---- > For asynchronous verification, the hub MUST consider other server > response codes (3xx, 4xx, and 5xx) to mean that the subscription > action was temporarily not verified. If the subscriber returns an HTTP > success (2xx) but the content body does not match the hub.challenge > parameter, the hub MUST consider this to be a temporary failure and > retry. The hub SHOULD retry verification a reasonable number of times > over the course of a longer time period (e.g., 6 hours) until a > definite acknowledgement (positive or negative) is received. If a > definite response still cannot be determined after this retry period, > the subscription action verification MUST be abandoned, leaving the > previous subscription state. > ---- > > What HTTP status code should be considered as a "definite negative > acknowledgement"?
http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#rfc.section.6.2.1 The subscriber MUST confirm that the hub.topic and hub.verify_token correspond to a pending subscription or unsubscription that it wishes to carry out. If so, the subscriber MUST respond with an HTTP success (2xx) code with a response body equal to the hub.challenge parameter. If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
