Page History
Div | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
...
...
...
...
...
...
...
Generates a HTTP digest header using the specified algorithm. When applied, a digest header is generated using the specified algorithm, and sent with the request. The generated header conforms with RFC3230 and RFC5843.
Info |
---|
Only one value is supported (no multi-value header). |
...
...
MD5
...
SHA
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Disable most of the path normalization. All escaping must be done manually, leading or trailing whitespaces are preserved.
Multiexcerpt include | ||||
---|---|---|---|---|
|
...
RESTOperation
...
MultiExcerptName | REST |
---|
...
Provide the HTTP method of this REST method should respond to.
...
- method name, if it is one of: GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS (with optional trailing '/')
- GET otherwise
...
Disable most of the path normalization. All escaping must be done manually, leading or trailing whitespaces are preserved.
Multiexcerpt | ||
---|---|---|
| ||
This is what still will be done, if isVerbatimPath is set to true:
|
...
...
Info | ||
---|---|---|
| ||
This attribute must be left unset if no Blob output parameters are used. In future versions, the effect of this attribute may be extended to other contexts as well. |
...
The xUML Runtime performs a verification of the content-type header for REST responses. Specify whether to return an error (HTTP 406, not acceptable) on responses with a content type that does not conform with the content types specified in Blob Body Content Type.
Refer to Handling Blobs in the REST Interface for a deeper explanation and some examples.
...
- Reject to perform adapter call if the header "content-type" does not match the values listed in Blob Body Content Type (default).
- Exception:
RESTLM/48: Request content type not declared as accepted by the service
...
Provide a list of content types this REST endpoint accepts. This must be a list of valid Accept headers as defined in RFC 7231.
Refer to Handling Blobs in the REST Interface for a deeper explanation and some examples.
Info | ||
---|---|---|
| ||
This attribute must be left unset if no Blob output parameters are used. In future versions, the effect of this attribute may be extended to other contexts as well. |
...
Specify whether to return an error on requests with a content type that does not conform with the content types specified in Accepted Request Content Type.
Refer to Handling Blobs in the REST Interface for a deeper explanation and some examples.
...
- Reject to perform adapter call if the header "accept" does not match the values
listed in Accepted Request Content Type (default).
- Exception:
Set "accept" header does not accept any of declared response content types
...
RESTParameter
...
MultiExcerptName | RESTParameter |
---|
...
...
With the REST Adapter, the xUML Runtime can handle JSON or XML as content types. The Runtime will parse either response content (JSON or XML) to a response object automatically.
You do not need to set any headers. If no headers are set, the Runtime will use JSON as a default format and set Accept header to application/json,text/json,application/xml;q=0.9,text/xml;q=0.9,*/*;q=0.8
.
Regarding response parsing, the xUML Runtime will process REST responses as follows:
...
...