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

Call out that extra fields in requests and responses are allowed #436

Merged
merged 4 commits into from
Mar 28, 2018
Merged

Call out that extra fields in requests and responses are allowed #436

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
affc85e
Call out that extra fields in requests and responses are allowed
Feb 1, 2018
3ed58b5
do it in just one spot
Feb 21, 2018
ca6a6b6
add an extensions property
Mar 6, 2018
63f881c
all in one spot again
Mar 20, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 13 additions & 4 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,18 @@ Service 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.

## Vendor Extension Fields

Senders of messages defined by this specification MAY include additional
fields within the JSON objects. When adding new fields, unique prefixes
SHOULD be used for the field names to reduce the chances of conflicts with
with future specification defined fields or other extensions.

Receivers of a messages defined by this specification that contain unknown
extension fields MUST ignore those fields and MUST NOT halt processing
of those messages due to the presence of those fields. Receiver are under
no obligation to understand or process unknown extension fields.

## Platform to Service Broker Authentication

While the communication between a Platform and Service Broker MAY be unsecure,
Expand Down Expand Up @@ -259,10 +271,7 @@ When a request to a Service Broker fails, the Service Broker MUST return an
appropriate HTTP response code. Where the specification defines the expected
response code, that response code MUST be used.

For error responses, the following fields are defined. Service Brokers MAY
include additional fields within the response. When adding new fields, Service
Brokers SHOULD use a unique prefix for the field names to reduce the chances of
conflict with future specification defined fields.
For error responses, the following fields are defined:

| Response Field | Type | Description |
| --- | --- | --- |
Expand Down