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
6.2: “MUST inform the subscriber by sending an HTTP [RFC7231] GET request to the subscriber's callback URL”
Suddenly no HTTPS? :)
Why not DELETE? That would make the semantics clearer, does not make REST people cringe, and implementations can still easily detect notification POSTs.
Why not DELETE? That would make the semantics clearer, does not make REST people cringe, and implementations can still easily detect notification POSTs.
As for HTTP vs HTTPS, this was not intended to restrict to HTTP URLs, so I've added an explicit mention of HTTPS in this case as well. This actually occurred in a few places so I made the changes there as well.
Suddenly no HTTPS? :)
Why not DELETE? That would make the semantics clearer, does not make REST people cringe, and implementations can still easily detect notification POSTs.
From #127 by @mkovatsc
The text was updated successfully, but these errors were encountered: