Show Content for Traffic Manager Errors
About
The Show Content for Traffic Manager Errors action is typically used in scenarios where, following a request to the vService, it is desired to display content only when a specific error code is selected by the TR7 LB/WAF (Traffic Manager) at the moment of the request.
How to Add?
To add the Show Content for Traffic Manager Errors action from TR7 ASP web interface, "Traffic Manager > Traffic Manipulation > Actions > Add" steps are followed. At the current page Show Content for Traffic Manager Errors is selected as an Action Type and the following form is shown.
Usable Types of
- HTTP
- L7 TCP
- Network
Arayüz
Show Content for Traffic Manager Errors Form
- Action Name
Name for the action is entered.
- Action Type
Show Content for Traffic Manager Errors is selected.
- Content Page
The Content Page to be shown to the client is selected. A new content page can also be added during the action addition step by clicking the Add button. For detailed information about content pages, click here.
- Error Codes
The expected error code from TR7 LB/WAF (Traffic Manager) is selected. Multiple error code selections can be made.
- List of HTTP Error Codes Supported by TR7
| Status Code | Status | Description |
|---|---|---|
| 400 | Client Error | Request Structure is Faulty |
| 401 | Client Error | Invalid Authentication |
| 403 | Client Erro | Page/Resource Forbidden |
| 404 | Client Error | Page/Resource Not Found |
| 405 | Client Error | Request Method Not Supported |
| 407 | Client Eror | Proxy Authentication Required |
| 408 | Client Errr | Request Timeout |
| 410 | Client Erro | Resource Permanently Gone |
| 413 | Client Error | Request Size Too Large |
| 425 | Client Error | Too Early |
| 429 | Client Error | Too Many Requests |
| 500 | Server Errors | Internal Server Error |
| 501 | Server Errors | Not Implemented |
| 502 | Server Errors | Bad Gateway |
| 503 | Server Errors | Service Unavailable |
| 504 | Server Errors | Gateway Timeout |
- Status Code
The HTTP Status Code with which the Content Page to be shown to the client will be returned is selected. By default, HTTP 200 Status Code is pre-selected. The table below lists all the HTTP status codes supported by TR7 that can be selected.
- Complete List of HTTP Status Codes Supported by TR7
| Status Code | Status | Description |
|---|---|---|
| 100 | Informational | Continue |
| 101 | Informational | Protocol Switch Confirmed |
| 102 | Informational | Method Processing |
| 103 | Informational | Response Headers Returned |
| 200 | Successful | OK |
| 201 | Successful | Resource Created on Server |
| 202 | Successful | Request Accepted But Not Yet Processed |
| 203 | Successful | Modified 200 OK Response |
| 204 | Successful | No Content Returned |
| 205 | Successful | Document View Should Reset |
| 206 | Successful | Partial Content Returned |
| 207 | Successful | Multi-Status |
| 208 | Successful | Already Reported |
| 226 | Successful | IM Used |
| 300 | Redirection | Multiple Choices |
| 301 | Redirection | Permanent Redirection |
| 302 | Redirection | Temporary Redirection |
| 303 | Redirection | GET Request Redirection |
| 304 | Redirection | Resources Not Modified |
| 305 | Redirection | Use Server Proxy |
| 306 | Redirection | Change Proxy/No Longer Used |
| 307 | Redirection | Temporary Redirect |
| 308 | Redirection | Permanent Redirect |
| 400 | Client Error | Request Structure is Faulty |
| 401 | Client Error | Invalid Authentication |
| 402 | Client Error | Payment Not Required |
| 403 | Client Error | Page/Resource Forbidden |
| 404 | Client Error | Page/Resource Not Found |
| 405 | Client Error | Request Method Not Supported |
| 406 | Client Error | Non-Matching Accept Header |
| 407 | Client Error | Proxy Authentication Required |
| 408 | Client Error | Request Timeout |
| 409 | Client Error | Conflict Exists |
| 410 | Client Error | Resource Permanently Gone |
| 411 | Client Error | Length Not Specified |
| 412 | Client Error | Preconditions Not Met |
| 413 | Client Error | Request Size Too Large |
| 414 | Client Error | URI Too Long |
| 415 | Client Error | Unsupported Media Type |
| 416 | Client Error | Requested Range Not Satisfiable |
| 417 | Client Error | Expectation Failed |
| 418 | Client Error | 418 |
| 419 | Client Error | 419 |
| 420 | Client Error | Method Error |
| 421 | Client Error | Misdirected Request |
| 422 | Client Error | Unprocessable Entity |
| 423 | Client Error | Resource Locked |
| 424 | Client Error | Dependency Error |
| 425 | Client Error | Too Early |
| 426 | Client Error | Upgrade Required |
| 428 | Client Error | Precondition Required |
| 429 | Client Error | Too Many Requests |
| 430 | Client Error | Request Header Fields Too Large (Shopify) |
| 431 | Client Error | Request Header Fields Too Large |
| 440 | Client Error | Session Timeout |
| 444 | Client Error | No Response |
| 449 | Client Error | Retry With |
| 450 | Client Error | Blocked by Windows Parental Controls |
| 451 | Client Error | Unavailable For Legal Reasons |
| 460 | Client Error | 460 |
| 463 | Client Error | 463 |
| 494 | Client Error | Request Header Too Large |
| 495 | Client Error | SSL Certificate Error |
| 496 | Client Error | SSL Certificate Required |
| 497 | Client Error | HTTP Request Sent to HTTPS Port |
| 498 | Client Error | Invalid Token (Esri) |
| 499 | Client Error | Client Closed Request (Nginx) |
| 500 | Server Errors | Internal Server Error |
| 501 | Server Errors | Not Implemented |
| 502 | Server Errors | Bad Gateway |
| 503 | Server Errors | Service Unavailable |
| 504 | Server Errors | Gateway Timeout |
| 505 | Server Errors | HTTP Version Not Supported |
| 506 | Server Errors | Variant Also Negotiates |
| 507 | Server Errors | Insufficient Storage |
| 508 | Server Errors | Loop Detected |
| 509 | Server Errors | Bandwidth Limit Exceeded (Apache Web Server/cPanel) |
| 510 | Server Errors | Not Extended |
| 511 | Server Errors | Network Authentication Required |
| 520 | Server Errors | Web Server Returned an Unknown Error |
| 521 | Server Errors | Web Server is Down |
| 522 | Server Errors | Connection Timed Out |
| 523 | Server Errors | Origin is Unreachable |
| 524 | Server Errors | A Timeout Occurred |
| 525 | Server Errors | SSL Handshake Failed |
| 526 | Server Errors | Invalid SSL Certificate |
| 529 | Server Errors | Site Overloaded |
| 530 | Server Errors | Site Frozen |
| 598 | Server Errors | Network Read Timeout Error |
| 599 | Server Errors | Network Read Timeout Error |
- Form Buttons
Add button can be clicked to add the configured action.
Add & Repeat button can be clicked to add the configured action. New similar actions can also be added without losing the current configuration by clicking this button. The following alert is shown when the button is clicked.
Condition Requirement
Show Content for Traffic Manager Errors action does not require a conditions.