Changes to make WebFinger RFC-conformant #193
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Use `application/jrd+json` content type for JRD responses. * Verify resource matches Postmarks account. * Use 404 status for unsupported resource URI scheme.
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
application/jrd+jsoncontent type for JRD responses.WebFinger uses 400 for malformed requests (where the URI syntax is invalid, the
resourceparameter is missing, or the URI query parameters are otherwise not conformant to the RFC). An unsupported resource URI scheme in a syntactically-valid URI isn't malformed. However, 404 makes sense given the resource is not known to the server.