> For the complete documentation index, see [llms.txt](https://docs.openappsec.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openappsec.io/troubleshooting/troubleshooting-guides/agent-not-recognizing-initial-http-requests.md).

# Agent Not Recognizing Initial HTTP Requests

The HTTP Transaction handler nano-service A process (or multiple instances, depending on load) that gets data for processing from the **Attachment**, executes open-appsec security logic, returns a verdict, and issues relevant logs.  

This service is fired when the first packets arrive at agents, Depending on the amount of NGINX / Kong services (typically the number of cores), we need at least one packet so we can fire up the transaction handler, meaning the first packets won't be blocked. 

* When starting as recommended in learn-detect mode this shouldn't affect you. 
* In a testing/demo environment when starting in prevent mode please run the needed number of request before testing the attack


---

# 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://docs.openappsec.io/troubleshooting/troubleshooting-guides/agent-not-recognizing-initial-http-requests.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.