[Openid-specs-risc] What happens to RFC8936 polling endpoints when stream status not enabled
Phillip Hunt
phil.hunt at independentid.com
Thu Jan 29 21:45:48 UTC 2026
Retgarding SSF spec 1.0 final and the profile of RFC8936...
What should happen at a transmitter’s polling endpoint when a stream has been suspended or disabled (e.g. administratively disabled by the SSF transmitter entity)
Would it:
* Respond with no events
* Not respond - cause a connection error - typically a client would probably retry
* Return 403 - forbidden
* Return 503 - Service Unavailable? - or should this be reserved for overload situations only?
* Return 400 - this is meant for badly formatted request per 8936
I am working on retry algorithm and now wondering what to expect when the stream is not enabled.
Should the SSF client then check the status endpoint? Is that endpoint maintained when a stream is disabled?
Thanks,
Phil
phil.hunt at independentid.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20260129/d347845a/attachment.htm>
More information about the Openid-specs-risc
mailing list