204 |
|
Access proxy was successfuly updated
|
401 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Unauthorized. |
403 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Unable to get permission. administrator permissions required |
404 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Access proxy specified by the access-proxy-identifier did not exist |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Listening port is not valid for this protocol |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Another proxy is already defined with the same listening port |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
No listening address type was specified |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The internal access proxy address does not match the destination type |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The external access proxy address does not match a member of the listening address types |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Only one HTTP_TUNNEL can be defined |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
An HTTP_TUNNEL cannot have any hops |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The access proxy config for this proxy type must have one next hop defined |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Destination address and address type do not match |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
A host header value is either missing or invalid |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The URI filter field is required when the server type is Other |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Access proxy id in body does no match the resource specified in the URL |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Cannot change transport value |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Cannot change protocol value |
412 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
This access proxy resource has changed on the server.
Note: The response will contain the ETag value and link that reflects
the server's access proxy resource in the HTTP response header.
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-access-proxy.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|
428 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-proxy.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|