HTTP Error

Proxy Error Logs are automatically collected and can be viewed in the HTTP Error tab in the Monitoring section of the Web UI.

These logs help you quickly identify the cause of failed or problematic requests, along with suggested remediations where available. This can speed up troubleshooting and reduce downtime.

⚠️ Beta Feature This feature is currently in beta and may be subject to changes. Functionality, configuration options, and behavior could change in future releases.

Types of HTTP Error Logs

There are two main types of events you may see in this tab:

1. Upstream Application Error

   • Indicates that the request reached the backend application, but the application returned an error.

   • Common causes: authentication failures, backend service issues, invalid API calls.

   • Example:

     • Event Name: Upstream Application Error

     • HTTP Response Code: 401 (Unauthorized)

     • Suggests that the backend refused the request, often due to missing or incorrect credentials.

2. Reverse Proxy Error

   • Indicates that the proxy itself rejected the request before it reached the backend.

   • Common causes: malformed requests, protocol errors, invalid headers.

   • Example:

     • Event Name: Reverse Proxy Error

     • HTTP Response Code: 400 (Bad Request)

     • Includes a Suggested Remediation, e.g., “Check request syntax and format; validate client input and HTTP headers.”

How to View the Logs

1. Go to the Monitoring section in the Web UI.

2. Select the HTTP Error tab.

1. Use filters (e.g., by Event Name, Date, Asset) to find relevant entries.

2. Review the details, including HTTP response codes, request path, and remediation suggestions.

These logs provide clear visibility into whether an error originated from your application or from the proxy layer, helping you focus troubleshooting in the right place.