无论是从全局的自动应答还是单独路由里配置的自动应答，都要重启higress的三个deploy才能生效吗

[yunhai20082008]

如题，我发现waf也是直接配不生效，重启deploy没试。无论是自动应答还是waf只要在web配好kubectl -n higress-system describe WasmPlugin xxxxx都是立即更改

[yunhai20082008]

配置waf后，gataway的控制台会提示一些错误
2025-04-15T05:09:45.464436Z error envoy wasm external/envoy/source/extensions/common/wasm/wasm_vm.cc:41 Failed to load Wasm module due to a missing import: wasi_snapshot_preview1.fd_pread thread=30

2025-04-15T05:09:45.464820Z error envoy wasm external/envoy/source/extensions/common/wasm/wasm.cc:151 Wasm VM failed Failed to initialize Wasm code thread=30

[CH3CHO]

你可以先看一下 waf-1.0.0 这个 WasmPlugin 里镜像的 tag。如果是 1.0.0 的话，可以先改成 1.0.1 看看。

[yunhai20082008]

ip-restriction 配置后是立即生效的

[CH3CHO]

配置自动应答之后，Gateway 有什么报错吗？

[yunhai20082008]

刚试了下，会出现info wasm fetching image plugins/custom-response from registry higress-registry.cn-hangzhou.cr.aliyuncs.com with tag 1.0.0。。。。改waf为1.0.1是只改1.0.0里面的url地址这一处，以oci开头的吗。像labels等其他的地方用把1.0.0改成1.0.1吗，我看gateway控制台在我改后打开waf的时候也fetch镜像了
.。。。改了之后等了一会出现下面问题
2025-04-15T05:40:29.914085Z info wasm fetching image plugins/custom-response from registry higress-registry.cn-hangzhou.cr.aliyuncs.com with tag 1.0.0

2025-04-15T05:49:13.621749Z info wasm fetching image plugins/waf from registry higress-registry.cn-hangzhou.cr.aliyuncs.com with tag 1.0.1

2025-04-15T05:49:32.956731Z error envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1401 wasm log: unknown directive "“secruleengine" line=12915 thread=30

2025-04-15T05:49:32.956840Z error envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1401 wasm log: [waf-plugin-go] Failed to create waf conf: invalid WAF config from string: unknown directive "“secruleengine" thread=30

2025-04-15T05:49:32.956868Z warning envoy wasm external/envoy/source/extensions/common/wasm/context.cc:1398 wasm log: [waf-plugin-go] parse rule config failed: failed to create waf conf thread=30

2025-04-15T05:49:32.956953Z error envoy wasm external/envoy/source/extensions/common/wasm/wasm.cc:151 Wasm VM failed Failed to configure base Wasm plugin thread=30

2025-04-15T05:49:32.963584Z warning envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:128 gRPC config for type.googleapis.com/envoy.config.core.v3.TypedExtensionConfig rejected: Unable to create Wasm HTTP filter higress-system.waf-1.0.0 thread=30

2025-04-15T05:49:32.967108Z warning envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:128 gRPC config for type.googleapis.com/envoy.config.core.v3.TypedExtensionConfig rejected: Unable to create Wasm HTTP filter higress-system.waf-1.0.0 thread=30

2025-04-15T05:49:32.967138Z warning envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:128 gRPC config for type.googleapis.com/envoy.config.core.v3.TypedExtensionConfig rejected: Unable to create Wasm HTTP filter higress-system.waf-1.0.0 thread=30

[CH3CHO]

label 不用改，改 url 就行。下面的日志已经是在初始化 waf 插件了，配置有个问题：

Failed to create waf conf: invalid WAF config from string: unknown directive "“secruleengine"

[yunhai20082008]

多谢了，我这个眼睛该治治了，调了两个小时愣是没看出来双引号有问题