Comments (7)
I may have been wrong to pull the HTTP 1.1 reference. HTTP/2 defers a lot of guidance to the HTTP 1.1 spec.
from cti-taxii2.
This seems reasonable, though I could also see an argument for it being a SHOULD.
from cti-taxii2.
I feel like any significant TAXII Server is going to have to sit behind a load balancer. It’ll be really difficult to handle the LB’s responses as JSON, especially in the Cloud. That’s why I’m hesitant to even use SHOULD.
from cti-taxii2.
This is in section 3.1. The text we are looking to change is:
TAXII responses with an HTTP error code (400-series and 500-series status codes, defined by sections 6.5 and 6.6 of [RFC7231]) that permit a response body (i.e. are not in response to a HEAD request) MUST contain an error message (see section 3.5.1) in the response body.
And we are looking to change the last MUST to be either a SHOULD or a MAY.
from cti-taxii2.
Does this also impact our Status Resource that is sent back with a 202 (Accepted) ?
from cti-taxii2.
No. It's not an error.
from cti-taxii2.
This changes was made in Section 3.1
Drew and I discussed this, and it seems like a MAY is the right way to go, since load balancers and cloud systems may need to do creative things with routing the error messages. The new text now says:
TAXII responses with an HTTP error code (400-series and 500-series status codes, defined by sections 6.5 and 6.6 of [RFC7231]) that permit a response body (i.e. are not in response to a HEAD request) MAY contain an error message (see section 3.5.1) in the response body.
from cti-taxii2.
Related Issues (20)
- Rename the spec_versions url filter parameter to be singular HOT 1
- Make the TAXII Envelope contain a list of objects not a bundle HOT 2
- Add text to explain status counts when server has yet to start processing request HOT 1
- Consider renaming the status value of pending to processing HOT 1
- What is the purpose of Discovery API roots having different domains in the list of api_roots ? HOT 2
- API Root Resource does not define the URL of the resource? HOT 2
- Typo in url prop of section 5.4 HOT 2
- Change integer to be 54 bits in size per RFC 7493 HOT 1
- If collections permission has false for CanRead and CanWrite, does user have permissions to see existence of Collection?
- RFE: Add additional Supported Fields to TAXII Filtering HOT 1
- Potential confusion with errors when adding duplicate objects
- Potential Confusion on Get Object Manifests
- Potentially misleading table in TAXII spec
- Typos in the TAXII spec
- Manifest & Versions Resource missing `next` Property HOT 1
- Additional URL query parameters
- Match field formatting
- "Incorrect" Spelling
- TAXII filtering is ambiguous when handling spec_version and version match fields
- Advanced filtering capability
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cti-taxii2.