Explanation | The identified filter failed to handle an event. A proxy-internal error response will be built. |
Action | Review the log for related reasons as to why the filter failed. If the problem persists, contact the filter's vendor. |
Explanation | The identified filter failed to handle an event. No error response will be built because the response is already committed. |
Action | Review the log for related reasons as to why the filter failed. If the problem persists, contact the filter's vendor. |
Explanation | A host for the error page application could not be found. |
Action | Make sure the error page application URI is located in an available webmodule or Routing Rule. |
Explanation | No logging will occur due to the unhandled event. |
Action | Make sure the specified log file name(s) are valid and accessible. |
Explanation | All of the required elements of the specified Routing Rule are not completely defined and can not be routed to. |
Action | Make sure a URI Group, virtual host, and routing action are specified in this Routing Rule. |
Explanation | Indicates the specified custom property has been successfully processed by the proxy. |
Action | None. |
Explanation | Indicates the specified custom property has been recognized by the proxy, but the proxy must be restarted for this value to become active. |
Action | Restart the proxy server if you require the custom property value to be operational at this time. |
Explanation | A URL received from a server is not formatted according to RFC 2396 |
Action | Correct the format of the specified URL. |
Explanation | Indicates one or both of the supplied URL patterns can not be parsed |
Action | Make sure the patterns do not contain any typos and are formatted according to RFC 2396 |
Explanation | The proxy server requires a specific configuration for its object cache. The proxy server can not start with this condition. |
Action | Either disable proxy server caching, or ensure the proxy server's object cache is configured to enable NIO support. |
Explanation | The HTTP Proxy is successfully responding to load balancer inquiries. |
Action | None |