Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DELETE for Section 6.2? #137

Open
aaronpk opened this issue Oct 25, 2017 · 1 comment
Open

DELETE for Section 6.2? #137

aaronpk opened this issue Oct 25, 2017 · 1 comment

Comments

@aaronpk
Copy link
Member

aaronpk commented Oct 25, 2017

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.


From #127 by @mkovatsc

aaronpk added a commit that referenced this issue Nov 16, 2017
@aaronpk
Copy link
Member Author

aaronpk commented Nov 16, 2017

Why not DELETE? That would make the semantics clearer, does not make REST people cringe, and implementations can still easily detect notification POSTs.

This has been discussed at length in #28 already, with the outcome being that this note was added to describe the spec's use of GET vs POST: https://www.w3.org/TR/websub/#verification-details

Suddenly no HTTPS? :)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant