Configure HTTP error templates to create custom error pages when HTTP proxy errors occur.
URL
GET https://<IP-address-of-SPS>/api/configuration/http/error_templates
Operations
Operations with the /http/error_templates endpoint include:
| Operation | HTTP method | URL | Notes | 
|---|---|---|---|
| Querying existing error templates | GET | /api/configuration/http/error_templates | |
| Creating a new error template with a custom logo | POST | /api/configuration/http/error_templates | 
 | 
| Updating an existing error template | PUT | /api/configuration/http/error_templates/<key> | 
 | 
| Querying error templates info | GET | /api/configuration/http/error_templates?info= | 
 | 
| Querying custom error template preview | GET | /api/configuration/http/error_templates?preview=&error_type=<type-of-the-error-template> | 
 | 
Sample request
The following command lists the available HTTP proxy error templates.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/http/error_templates
Response
The following is a sample response received when available HTTP proxy error templates are queried.
{
     "name": "Template_with_logo",
     "color": "#123456",
     "logo": "<'logo_id' from the response of the first creation>",
     "brand_name": "Noname brand",
     "md_contents": {
       "auth": "Custom auth failed markdown content.",
       "badcontent": "Custom bad content error markdown content.",
       "clientsyntax": "Custom client syntax error markdown content.",
       "clienttimeout": "Custom client timeout error markdown content.",
       "connecterror": "Custom connection error markdown content.",
       "ftperror": "Custom FTP error markdown content.",
       "internal": "Custom internal error markdown content.",
       "invalidurl": "Custom invalid URL markdown content.",
       "ioerror": "Custom I/O error markdown content.",
       "policysyntax": "Custom policy syntax error markdown content.",
       "policyviolation": "Custom policy violation error markdown content.",
       "redirect": "Custom redirect markdown content.",
       "serversyntax": "Custom server syntax error markdown content.",
       "servertimeout": "Custom server timeout error markdown content."
     }
    }
The following is a sample response received when HTTP proxy error template information is queried with /api/configuration/http/error_templates?info=.
{
     "error_type_names": {
       "auth": "Authentication Failed",
       "badcontent": "Bad Content",
       "clientsyntax": "Client Syntax",
       "clienttimeout": "Client Timeout",
       "connecterror": "Connection Error",
       "ftperror": "FTP Error",
       "internal": "Internal Error",
       "invalidurl": "Invalid URL",
       "ioerror": "I/O Error",
       "policysyntax": "Policy Syntax",
       "policyviolation": "Policy Violation",
       "redirect": "Redirect",
       "serversyntax": "Server Syntax",
       "servertimeout": "Server Timeout"
     }
    }
Elements of the response message include:
| Element | Type | Description | Notes | 
|---|---|---|---|
| name | string | The name of the template. | 
 | 
| color | number | The color of the brand and links appearing in the error template. | The value is given in hex color code. | 
| logo | string? union? | The identifier of the logo. | The value of the logo can be 'null'. | 
| brand_name | string | The name of the brand. | 
 | 
| md_contents | object | Contains a list of error templates written in Markdown. | 
 | 
| md_contents.auth | string | The content of the Authentication failed error template in Markdown. | 
 | 
| md_contents.badcontent | string | The content of the Bad content error template in Markdown. | 
 | 
| md_contents.clientsyntax | string | The content of the Client syntax error template in Markdown. | 
 | 
| md_contents.clienttimeout | string | The content of the Client timeout error template in Markdown. | 
 | 
| md_contents.connecterror | string | The content of the Connect error error template in Markdown. | 
 | 
| md_contents.ftperror | string | The content of the FTP error error template in Markdown. | 
 | 
| md_contents.internal | string | The content of the Internal error error template in Markdown. | 
 | 
| md_contents.invalidurl | string | The content of the Invalid URL error template in Markdown. | 
 | 
| md_contents.ioerror | string | The content of the IO error error template in Markdown. | 
 | 
| md_contents.policysyntax | string | The content of the Policy syntax error template in Markdown. | 
 | 
| md_contents.policyviolation | string | The content of the Policy violation error template in Markdown. | 
 | 
| md_contents.redirect | string | The content of the Redirect error template in Markdown. | 
 | 
| md_contents.serversyntax | string | The content of the Server syntax error template in Markdown. | 
 | 
| md_contents.servertimeout | string | The content of the Server timeout error template in Markdown. | 
 | 
For details of the meta object, see Message format.
HTTP response codes
HTTP response codes comprise of standard or endpoint-specific HTTP status and error codes. The following table lists the endpoint-specific HTTP response codes for this request.
| HTTP response code | Status/Error | Description | 
|---|---|---|
| 400 | NotSupportedProxyErrorType | Preview could not be created. The used error type is not supported. Use an error type from the following list: Authentication failed, Bad content, Client syntax, Client timeout, Connect error, FTP error, Internal, Invalid URL, IO error, Policy syntax, Policy violation, Redirect, Server syntax, Server timeout. | 
For more information and a complete list of standard HTTP response codes, see Application level error codes.
