shreemaan-abhishek commented on PR #13648:
URL: https://github.com/apache/apisix/pull/13648#issuecomment-4874572605

   Added a regression test (`TEST 22` in `t/plugin/loggly.t`) covering exactly 
this case:
   
   - Two routes with distinct HTTP-bulk loggly configs (`customer_token` 
`token-a`/`token-b`, tags `aaa`/`bbb`).
   - Both send one entry each, which buffer before either batch flushes 
(`inactive_timeout: 1`, default batch size), so the two batch processors flush 
after both `log()` calls have run.
   - The mock bulk endpoint captures the token from the request path and the 
`X-LOGGLY-TAG` header, and the test asserts each batch arrives with its own 
token/tags.
   
   This fails on the previous behavior: the shared module-level 
`handle_http_payload` was left holding whichever request ran `log()` last, so 
both batches were sent with `token-b` and the `token-a` assertion never 
matches. With this PR each batch processor binds its own `conf`, so both 
assertions pass.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to