3.6.5 Message Processing Events and Sequencing Rules
The proxy MAY use the server store to save and retrieve information about the proxy service or about applications published through the proxy. The server provides resources to set and retrieve information based on a key/value pair entry model.
The following resources are available to store custom proxy configuration on the server.
|
Resource |
Description |
|---|---|
|
Proxy/WebApplicationProxy/Store |
Resource used to retrieve all entries in the store. |
|
Proxy/WebApplicationProxy/Store/{Key} |
Resource used to add, retrieve, remove, or modify an entry in the store. |
The responses to all the operations can result in the following status codes.
|
Status code |
Description |
|---|---|
|
200 |
The operation has succeeded. |
|
400 |
The request is not valid. |
|
401 |
Unauthorized for the specified user credentials or for the client TLS certificate. |
|
404 |
The object does not exist. |
|
405 |
Invalid verb used in request (GET, DELETE, POST, PUT). |
|
409 |
The object already exists. |
|
412 |
A precondition failed. |
|
500 |
Version is not specified where required or any other internal error. |
|
501 |
Version specified (api-version) is invalid (only valid value is 1). |
For all operations in this section, the server requires authenticating the proxy using client TLS authentication [RFC2246]. The server MUST validate that the certificate that is presented by the proxy during client TLS authentication can be validated by one of the values of [Server State].ProxyTrustedCertificates. If the certificate cannot be validated, the server MUST return an HTTP error code of 401.