【bug】higress 中包含特殊符号复杂的header 值这是无效；且有复杂值，重启gateway 后 直接无法匹配路由 || [bug] higress contains special symbols and complex header values, which is invalid; and there are complex values. After restarting the gateway, the route cannot be matched directly.

[zaoyong]

1、当我在路由，策略中自定义header 值，value 比较复杂包含特殊字符时，无法带到目标服务，且无日志说明输出
header 示例测试值：Nn9ZP4@Kg5e9A%lNrK

2、配置了复杂的header时， 重启gateway 后，会直接导致直接无法匹配路由，删除复杂的header 值恢复正常路由匹配；

麻烦尽快修复，无法完成自定义设置

---

1. When I customize the header value in routing and policies, and the value is complex and contains special characters, it cannot be brought to the target service, and there is no log description output.
   Header sample test value: Nn9ZP4@Kg5e9A%lNrK

2. When a complex header is configured, restarting the gateway will directly result in the inability to match routes. Delete the complex header value to restore normal route matching;

Please fix it as soon as possible. Custom settings cannot be completed

[CH3CHO]

可以先用 transformer 插件试一下。

---

You can try it with the transformer plug-in first.

[CH3CHO]

2026-04-24T04:55:36.844142Z	warning	envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:143	gRPC config for type.googleapis.com/envoy.config.route.v3.RouteConfiguration rejected: Incorrect configuration: N@n9%ZP4Kg5e9AlNrK. Couldn't find valid command at position 4	thread=31

"requestHeadersToAdd": [
    {
        "header": {
            "key": "X-KEY",
            "value": "N@n9%ZP4Kg5e9AlNrK"
        }
    }
]

请 @EndlessSeeker 看一下。