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

Add clarity for media endpoint discovery #118

Open
MaybeThisIsRu opened this issue Jul 23, 2020 · 0 comments
Open

Add clarity for media endpoint discovery #118

MaybeThisIsRu opened this issue Jul 23, 2020 · 0 comments

Comments

@MaybeThisIsRu
Copy link

In 3.6.1, the spec says the server MUST include media-endpoint in a config request:

To advertise that the Micropub endpoint supports a Media Endpoint, the server MUST include a key called media-endpoint with a value of the full URL of the Media Endpoint in the Micropub configuration request. Clients MUST NOT assume the Media Endpoint is on the same domain as the Micropub endpoint.

In 3.7.1, the spec says the server SHOULD include media-endpoint in a config request:

The server SHOULD include the following information in the configuration response.

  • The list of syndication endpoints supported, in a property called syndicate-to (see Syndication Targets for details on the structure of the response)
  • The Media Endpoint if supported, in a property called media-endpoint

In either section, the response is only to include a media-endpoint if it is supported. However, the language used makes it hard to decide whether a server must, or must not. It would be great if this could be spelled out clearly and uniformly.

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

No branches or pull requests

1 participant