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

X-Broker-API-Version Header Check vs Spec Definition #3

Open
jeremyrickard opened this issue Nov 29, 2017 · 3 comments
Open

X-Broker-API-Version Header Check vs Spec Definition #3

jeremyrickard opened this issue Nov 29, 2017 · 3 comments

Comments

@jeremyrickard
Copy link

The following check seems to be imposing a requirement that the spec does not actually impose:

should reject requests without X-Broker-API-Version header with 412

The Open Service Broker Spec states:

Requests from the platform to the service broker MUST contain a header that declares the version number of the Service Broker API that the marketplace will use:

This header allows brokers to reject requests from marketplaces for versions they do not support. While minor API revisions will always be additive, it is possible that brokers depend on a feature from a newer version of the API that is supported by the platform. In this scenario the broker MAY reject the request with 412 Precondition Failed and provide a message that informs the operator of the API version that is to be used instead.

Note that this doesn't actually state the brokers MUST fail the request (it doesn't define the behavior so it''s ambiguous).

@Haishi2016
Copy link
Contributor

What would be a good fix to this, to make this part configurable in the test config, i.e. "check for X-Broker-API-Version header" (true or false)?

@eruvanos
Copy link

Requests from the platform to the service broker MUST contain a header that declares the version number of the Service Broker API that the marketplace will use...

I think this means, that requests without that header are invalid requests. That would be a 400 BadRequest.

What do you think?

@leonwanghui
Copy link
Collaborator

@zhongyi-zhang @norshtein Any thought?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Inbox
Development

No branches or pull requests

4 participants