dingshuangxi888 opened a new issue, #7702: URL: https://github.com/apache/rocketmq/issues/7702
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment Linux ### RocketMQ version develop ### JDK Version JDK11 ### Describe the Bug When parsing the PPV2 protocol and setting the TLS contents as gRPC attributes, gRPC will log the following messages. To avoid excessive logging, filter out content that does not conform to ASCII. ``` WARNING: Metadata key=proxy_protocol_tlv_0x03, value=[61, 12, 109] contains invalid ASCII characters Dec 26, 2023 8:11:08 PM io.grpc.internal.TransportFrameUtil toHttp2Headers WARNING: Metadata key=proxy_protocol_tlv_0x03, value=[61, 12, 109] contains invalid ASCII characters Dec 26, 2023 8:11:08 PM io.grpc.internal.TransportFrameUtil toHttp2Headers WARNING: Metadata key=proxy_protocol_tlv_0x03, value=[61, 12, 109] contains invalid ASCII characters Dec 26, 2023 8:11:08 PM io.grpc.internal.TransportFrameUtil toHttp2Headers WARNING: Metadata key=proxy_protocol_tlv_0x03, value=[61, 12, 109] contains invalid ASCII characters ``` ### Steps to Reproduce 1. Open the ppv2 protocol 2. Send ppv2 message with tls data [61, 12, 109] 3. Check the log ### What Did You Expect to See? The ppv2 tls data will be fiter if it is not ASCII. ### What Did You See Instead? No. ### Additional Context _No response_ -- 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]
