search

w3c / web-annotation

Web Annotation Working Group repository, see README for links to specs
https://w3c.github.io/web-annotation/
Other
141 stars 30 forks source link

Clarify distinction between OPTIONS and GET/HEAD #367

Closed azaroth42 closed 7 years ago

azaroth42 commented 7 years ago

While all three MUST be supported, the header and body requirements aren't as clear as they could be in the following text (Protocol section 4.1).

For example, OPTIONS doesn't need to have Content related headers, but HEAD and GET do, and all of them need the CORS headers.

Thanks (again) to @mattmcgrattan!

halindrome commented 7 years ago

I agree with this, but note that the CORS stuff is ONLY required when there is an origin issue. So for a private annotation client accessing a private annotation server...

On the other hand, since the whole point of this protocol is that any client can access any server, I think it is reasonable to require that servers expose the required headers. And that requires the correct CORS header settings.