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

Jump to bottom

Missing reference in content negotiation #54

Closed
jordan2175 opened this issue Feb 22, 2018 · 2 comments
Closed

Missing reference in content negotiation #54

jordan2175 opened this issue Feb 22, 2018 · 2 comments
Labels
Status: Closed Done Target: TAXII-2.1 Type: Clarification
Projects
TAXII-2.1
Milestone
2.1-CSD01-WD01

Comments

@jordan2175
Copy link

In section 1.4.7 we were missing a reference to RFC6838 for how to use the version parameter. The proposed text is:

This specification uses HTTP content negotiation [RFC7231] and a version parameter as defined in [RFC6838] section 4.3.
@jordan2175 jordan2175 added this to the 2.1-CSD01 milestone Feb 22, 2018
@johnwunder
Copy link

The new text in the draft for this looks good to me.

@jordan2175
Copy link
Author

The references section in 1.4.7 now looks like:

This specification uses media types (section 3.1.1.1 of [RFC7231]) and an optional version parameter in the HTTP Accept header (section 5.3.2 of [RFC7231]) and Content-Type header (section 3.1.1.5 of [RFC7231]) to perform HTTP content negotiation as defined in [RFC7231].

In addition to the following media types, this specification defines an optional version parameter per the guidelines as defined in section 4.3 of [RFC6838].

@jordan2175 jordan2175 added this to Done in TAXII-2.1 Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Closed Done Target: TAXII-2.1 Type: Clarification
Projects
No open projects
TAXII-2.1
  
Done
Milestone
2.1-CSD01-WD01
Development

No branches or pull requests
2 participants
@johnwunder @jordan2175