Clarify the use and discovery of HTTPS hubs

Tallefer / pubsubhubbub

Automatically exported from code.google.com/p/pubsubhubbub

Other

0 stars 0 forks source link

Clarify the use and discovery of HTTPS hubs #31

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

SUMMARY:

Right now we don't say much about HTTPS in the spec. We should explain in
more detail why it's good. We should also talk about how the
atom:link[@rel="hub"] can be a non-https HUB link, and it's up to
subscribers to test the other scheme if they want to have a secure
subscription. But publishers may also only advertise the HTTPS url. I'm not
sure if this should be a best practice or a requirement.

Original issue reported on code.google.com by bslatkin on 15 Jul 2009 at 7:39

GoogleCodeExporter commented 9 years ago

Should the Hub URL always be the https one? Or should subscribers have to guess 
that
they also allow HTTPS? My guess is the latter, because this allow for the 
stupidest
clients that don't support HTTPS and are just passing along parameters without 
much
attention to detail.

Original comment by bslatkin on 27 Aug 2009 at 3:51

Changed state: Accepted
Added labels: spec0.2

GoogleCodeExporter commented 9 years ago

Addressed in 0.2

Original comment by bslatkin on 2 Sep 2009 at 1:21

Changed state: Fixed