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
PreviousAgent Fails to Recognize HTTP Transactions with NGINXNextHandling Large Requests (413 Responses)
Last updated