DokiDoki1103 commented on issue #2044:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/2044#issuecomment-1813843173

    Dear sister, I still need your help
    
     I configured yaml to enable firewall plugin support for a certain route, 
but it reported an error 
     
   ```
   apiVersion: apisix.apache.org/v2
   kind: ApisixRoute
   metadata:
     name: httpbin-route
   spec:
     http:
     - name: route-ip
       plugins:
       - name: coraza-filter
         enable: true
         config:
           default_directives: "default"
           directives_map:
             defalut: 
             - "SecDebugLogLevel 9"
             - "SecRuleEngine On"
             - "Include @crs-setup-demo-conf"
             - "Include @owasp_crs/*.conf"
       match:
         hosts:
         - test.lyck6.cn
         paths:
         - "/ip"
       upstreams:
       - name: httpbin-upstream
   ```
   
    The error is because the plugin was not found 
   
   ```
   Events:
     Type     Reason               Age                   From           Message
     ----     ------               ----                  ----           -------
     Warning  ResourceSyncAborted  25s (x51 over 5m30s)  ApisixIngress  
ApisixIngress synced failed, with error: 1 error occurred:
              * unknown plugin [coraza-filter]
   ```
   
   
   Then I will configure configMap to support plugins, which is the document I 
referenced
   
   
   https://apisix.apache.org/blog/2023/09/08/APISIX-integrates-with-Coraza/
   
   <img width="639" alt="图片" 
src="https://github.com/apache/apisix-ingress-controller/assets/62740231/5c6756d1-ff4d-4fd6-9167-56b457079ace";>
   
   There is a path that I don't know what I should fill in
   
   
   ```/Home/ubuntu/coraza proxy wasm/build/main.wasm```
   
   
   
   The path I write by default does not work, do I still have any configuration 
errors?
   
   


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