Aias00 opened a new issue, #6634: URL: https://github.com/apache/shenyu/issues/6634
- Severity: High - Location: `shenyu-plugin/shenyu-plugin-security/shenyu-plugin-sign/src/main/java/org/apache/shenyu/plugin/sign/service/ComposableSignService.java:229` - Description: After successful signature verification, `handleExchange` is meant to forward the configured `appParam` to the upstream as the `appParam` request header. The implementation does `.ifPresent(param -> exchange.getRequest().mutate().headers(httpHeaders -> httpHeaders.set(Constants.APP_PARAM, param)).build());`. `ServerHttpRequest.mutate()` returns a builder whose `.build()` produces a *new* `ServerHttpRequest` — but that built request is the lambda's return value and is thrown away by `ifPresent`. It is never stored back into the exchange, and `handleExchange` (return type `void`) never propagates a new exchange to the chain. `SignPlugin.doExecute` then calls `chain.execute(exchange)` on the original, unmutated exchange. - Impact: The per-app `paramDataList`/`appParam` feature is completely non-functional: configured app parameters are computed and then dropped — the `appParam` header never reaches the upstream. - Suggested fix: Directly mutate the original request's headers: `.ifPresent(param -> exchange.getRequest().getHeaders().set(Constants.APP_PARAM, param));` — or restructure `handleExchange` to return a mutated `ServerWebExchange` and have `SignPlugin` execute the chain on it. - Confidence: High - Related existing: none --- _Identified during the 2026-08-02 deep re-scan; full list in [`docs/scan2-2026-08-02/00-consolidated-critical-high.md`](docs/scan2-2026-08-02/00-consolidated-critical-high.md)._ -- 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]
