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.

Sign up for GitHub

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

Figure out how to support TAXII 2.1 #41

Closed
clenk opened this issue Jun 5, 2018 · 1 comment
Closed

Figure out how to support TAXII 2.1 #41

clenk opened this issue Jun 5, 2018 · 1 comment
Labels
question
Milestone
2.0.0

Comments

@clenk
Copy link
Contributor

clenk commented Jun 5, 2018

Hopefully we can support all versions simultaneously, but we could also support different versions of the spec in different versions of the client. This may mean sending multiple media types in the accept header.
@gtback gtback added the question label Jul 5, 2018
@clenk clenk mentioned this issue Jun 3, 2019
Open
@emmanvg
Copy link
Contributor

emmanvg commented Apr 2, 2020

Took same approach as the one in stix2 to support different versions simultaneously. All components from TAXII 2.0 live under v20 similarly for TAXII 2.1 as v21. Shared structures moved into common.py. The clients will not send multiple media types and each expect a response based on the specific version of the specification.

@emmanvg emmanvg closed this as completed Apr 2, 2020
@emmanvg emmanvg added this to the 2.0.0 milestone Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
3 participants
@clenk @gtback @emmanvg