search

Tallefer / pubsubhubbub

Automatically exported from code.google.com/p/pubsubhubbub
Other
0 stars 0 forks source link

Protocol: Subscription Validation and Verification of Intent should use POST #149

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Protocol: Subscription Validation and Verification of Intent should use POST

SUMMARY:

The Hub should use HTTP POST when performing Subscription Validation and 
Verification of Intent.

RELEVANT SECTION:  5.2 and 5.3

COMMENT/REQUEST:

Both these requests are specified as using HTTP GET. However, HTTP GET is 
supposed to be "idempotent"--and not cause changes on the server. It's obvious 
that these situations do cause the Subscriber's state to change.

For Subscription Validation, a "hub.mode" of "denied" should cause the 
Subscriber to record a failure for the relevant Subscription Request.

For Verification of Intent, the proper parameters will likely cause the 
Subscriber to record that the Subscription has been activated or deactivated. 
In the latter case, the Subscriber will probably delete the record of that 
Subscription from its database.

Furthermore, HTTP GETs are cachable, and might be cached by intermediary 
caches. This would prevent a Subscriber from trying to request the same 
Subscription, say after a failure. HTTP POSTs are NOT cacheable, and would not 
be subject to this potential problem.

Original issue reported on code.google.com by j...@andersoninnovative.com on 24 May 2014 at 1:11

GoogleCodeExporter commented 9 years ago 
Please, feel free to use the Github page to report issues with the PubSubHbbub 
protocol :) 
https://github.com/pubsubhubbub/PubSubHubbub/issues?direction=desc&sort=created&
state=open

Original comment by julien.g...@gmail.com on 30 May 2014 at 4:08