pilichoumao opened a new issue, #6614: URL: https://github.com/apache/rocketmq-dashboard/issues/6614
### Before Creating the Bug Report - [x] Searched existing issues/PRs; this is the frontend follow-up to merged #6064. - [x] This defect is in RocketMQ Studio. - [x] Reproduced on current rocketmq-studio sources. ### Studio Version rocketmq-studio at 779b8c0e7aed2396d3cc72743dcd544ea48e9ae6. ### Runtime Environment Ubuntu 24.04 ECS, Node 20.20.2, Vitest/jsdom using the actual TopicPage and payload-preview sources. ### Connected RocketMQ Cluster Apache/native send path. No live broker was required for the frontend reproduction; the backend already rejects these inputs before acquiring clients. ### Describe the Bug The native message payload precheck reports encodability for property separators which the Apache backend rejects with 400 after #6064. It checks property format/duplicates/size but not U+0002 in Tag/Key/property values, or U+0001/U+0002 in property names. Both realtime preview and submit use this helper. ### Steps to Reproduce 1. Select an Apache instance and open a normal topic's Send dialog. 2. Enter a JSON body and a business property whose value contains an embedded U+0002. 3. Observe no blocking precheck issue; submitting reaches the API boundary instead of being stopped by the precheck. 4. Repeat with U+0001/U+0002 in a property name or U+0002 in Tag/Key, including pasted property text. ### What Did You Expect to See? The realtime preview and submit precheck should agree with the existing native backend policy and stop the request locally. U+0001 inside property values remains legal, as do commas, Unicode and equals signs. Do not apply Apache wire restrictions to unverified cloud-provider paths or alter nonblocking reserved-property warnings. ### What Did You See Instead? ECS helper regressions: six invalid cases fail on baseline; two legal controls pass; the prototype passes all eight. Through the actual TopicPage dialog, baseline has one failed blocking case and one passed legal send control; the prototype passes both and does not call the send service for the invalid property. ### Additional Context #6064 already protects native backend sends. This is a frontend consistency gap, not a new backend persistence bypass. #6277 tests reserved-name warnings, #5572 localizes existing precheck copy, and #6381 preserves nonblank property values; those are adjacent but different work. Proposed scope: opt into native wire validation based on the selected Apache vendor in both analysis calls; add localized blocking issue text and field detail; preserve legal values, cloud paths and existing warnings; validate helper contracts and real page submission paths, then run tsc -b, lint, build and license checks on ECS. -- 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]
