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

Returning Accept-Profile in HTTP OPTIONS response #677

Closed
kamhayfung opened this issue Jan 22, 2019 · 6 comments
Closed

Returning Accept-Profile in HTTP OPTIONS response #677

kamhayfung opened this issue Jan 22, 2019 · 6 comments
Assignees
Labels
due for closing Issue that is going to be closed if there are no objection within 6 days feedback Issues stemming from external feedback to the WG profile-negotiation
Milestone

Comments

@kamhayfung
Copy link

kamhayfung commented Jan 22, 2019

In 7.1.1.1 Example 1 (https://www.w3.org/TR/dx-prof-conneg/#listprofileshttpoptions), Accept-Profile, in conjunction with Content-Profile, should also be returned by the server where applicable. These two headers complement each other indicating what a server can receive and produce.

@nicholascar nicholascar added profile-negotiation feedback Issues stemming from external feedback to the WG labels Jan 22, 2019
@nicholascar nicholascar added this to the Conneg 2PWD milestone Jan 22, 2019
@nicholascar
Copy link
Contributor

Subgroup meeting 2019-02-14: discussed they understand this issue to force the spec to ensure symmetry for getting & sending (GET & POST) content

larsgsvensson added a commit that referenced this issue Feb 14, 2019
Added an Accept-Profile header to the example for the use of HTTP OPTIONS
and added some text clarifying that Accept-Profile in an OPTIONS response is for the case when a server accepts PUT, POST or PATCH for a resource
Addresses #677
@nicholascar
Copy link
Contributor

Addressed by PR #757

@kamhayfung
Copy link
Author

The commit looks good to me.

@larsgsvensson
Copy link
Contributor

Thanks for the feedback, Kam. In the CNEG meeting yesterday we decided to remove the use of OPTIONS altogether (cf #510). Bit of an irony, I admit...

@larsgsvensson larsgsvensson added the due for closing Issue that is going to be closed if there are no objection within 6 days label Feb 21, 2019
@nicholascar
Copy link
Contributor

Addressed by PR #781

@kamhayfung
Copy link
Author

No worries. I'll look into the Link header for our needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
due for closing Issue that is going to be closed if there are no objection within 6 days feedback Issues stemming from external feedback to the WG profile-negotiation
Projects
None yet
Development

No branches or pull requests

3 participants