> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/getting-started/monitor-events/http-error.md).

# 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.

{% hint style="warning" %}
**⚠️ Beta Feature**\
This feature is currently in **beta** and may be subject to changes. Functionality, configuration options, and behavior could change in future releases. 
{% endhint %}

#### 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.

<figure><img src="/files/tt2hMPVNivY5S4SbbAcL" alt=""><figcaption></figcaption></figure>

3. Use filters (e.g., by Event Name, Date, Asset) to find relevant entries.
4. 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://waf-doc.inext.checkpoint.com/getting-started/monitor-events/http-error.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.