Aias00 opened a new issue, #1022:
URL: https://github.com/apache/rocketmq-dashboard/issues/1022

   ## Problem
   
   The message-query API accepts unbounded and invalid time ranges, then 
performs per-queue pulls. Returned message records also decode the entire 
message body as UTF-8 and expose all properties without a response-size 
contract.
   
   ## Impact
   
   Large or binary messages and broad time ranges can cause excessive work, 
oversized responses, and unusable message detail views.
   
   ## Scope
   
   - Reject reversed or excessively broad topic-query windows with a structured 
400 response.
   - Preserve the existing lookup behavior for message-id and key queries.
   - Bound message body/property serialization and expose size, 
encoding/truncation metadata so callers can distinguish a shortened display 
value from the raw message.
   - Add focused regression coverage.
   
   ## Track
   
   Track 1 / BASE-01 message query and diagnostics.


-- 
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]

Reply via email to