Aias00 opened a new issue, #860: URL: https://github.com/apache/rocketmq-dashboard/issues/860
### What happened? `POST /api/clusters/config/update` accepts the JSON literal `null` as the request body. Spring can deserialize that into a null DTO and the controller currently forwards it to `ClusterService.updateClusterConfig`, which can surface an internal null-handling error instead of a clear client error. ### Why this matters Cluster configuration is part of the RocketMQ Studio control-plane workflow. Invalid write requests should be rejected at the API boundary with a stable 400 response so callers do not accidentally trigger service-layer null dereferences. ### Expected behavior The endpoint should reject a null request body with HTTP 400 and should not call the service layer. ### Scope RocketMQ Studio track 1 / ARCH-01 cluster configuration management hardening. -- 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]
