netty proxy发送未编程的非安全DirectByTebuf剪切包 这个问题不是用英语写的。通过谷歌翻译的时候也不会显得太热。。。特别是在没有密码的情况下。谢谢，等一下。 I meet a very strange problem when I us
netty proxy发送未编程的非安全DirectByTebuf剪切包netty proxy发送未编程的非安全DirectByTebuf剪切包 这个问题不是用英语写的。通过谷歌翻译的时候也不会显得太热。。。特别是在没有密码的情况下。谢谢，等一下。 I meet a very strange problem when I us,proxy,netty,Proxy,Netty,netty proxy发送未编程的非安全DirectByTebuf剪切包 这个问题不是用英语写的。通过谷歌翻译的时候也不会显得太热。。。特别是在没有密码的情况下。谢谢，等一下。 I meet a very strange problem when I use netty proxy to develop programs and I hope you can help me solve this problem. The details of the problem are as foll
这个问题不是用英语写的。通过谷歌翻译的时候也不会显得太热。。。特别是在没有密码的情况下。谢谢，等一下。 I meet a very strange problem when I use netty proxy to develop programs and I hope you can help me solve this problem. The details of the problem are as follows: Use the proxy package in the folder of example, proxyA connect proxyB, proxyA encrypt bytes-->HexDumpProxyFrontendHandler ===> proxyB HexDumpProxyFrontendHandler --> decryption when went back, ProxyB encrypt bytes-->HexDumpProxyBackendHandler ===> proxyA HexDumpProxyBackendHandler --> decryption When proxyA and proxyB are both in windows operating system, there is no problem and channelRead is UnpooledHeapByteBuf. However, when proxyA is in windows operating system and proxyB is in linux operating system, it goes wrong and channelRead becames UnpooledUnsafeDirectByteBuf. Turns out under this situation, UnpooledUnsafeDirectByteBuf is cut into many data packets. I want to know how to write code to avoid this problem?