-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fetch methods for app parameter #94
Comments
never tried to use pass by a header, wanna try using http-request set-var instead? |
I've already tried with no success: It seems the filter is getting the 'raw' input request without any previous modifications done. As I want to use different configs for different paths I think the only way will be tu use acl in spoa. If you've got any other idea... |
If you use event on-frontend-http-request, then works as intended:
|
Using haproxy 2.8.9 I had to use proc.var_name instead of rtx.var_name. I wanted to use a variable for the app_name, based on hdr(host), so in frontend:
In /etc/haproxy/coraza.conf:
It is working fine with |
Is this still an issue? It seems more of a haproxy config issue then smth related to coraza-spoa, but you should be able to set a txn-variable based on the header and use that for coraza. Please reopen if help is still needed |
Related to #92, is there any other fetch method that can be used? I tried to set a new header and try to get it into spoe
app
parameter without success.Haproxy frontend
http-request add-header X-App open
SPOE
spoe-message coraza-req args app=req.hdr(X-App) id=unique-id src-ip=src...
And coraza logs:
{"level":"debug","ts":1699303677.986173,"msg":"application not found, using default","application":"","default":"open"}
(of course, I have two apps that I want to set up different)
UPDATE: The header is not being added in haproxy. Is this an expected behaviour when using spoe filters?
The text was updated successfully, but these errors were encountered: