Special Characters in Responses

Responses from the server may contain special characters that cannot be displayed directly in an XML document. Such characters are replaced with character entity references, or predefined entities. For example, resource representations of VM guest OS file systems and responses from the query service and lookup service contain the '&' character entity reference instead of the ‘&’ character itself.

HTTP responses received from Veeam Backup Enterprise Manager REST API may contain the following character entity references:

The example below represents a list of links in the paginated response from the query service. The ‘&’ (ampersand) character used as a separator for query parameters in the query string is replaced with the '&' character entity reference.

When the client parses a response and retrieves a link that contains a character entity reference, the client must replace the character entity reference with the character itself before using the link in a request. If the client sends a request that contains a character entity reference, the server may ignore the subsequent parameter while processing the request or completely fail to process the request.