Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#号后内容被吞 #32

Closed
XYZliang opened this issue Jan 27, 2022 · 2 comments
Closed

#号后内容被吞 #32

XYZliang opened this issue Jan 27, 2022 · 2 comments

Comments

@XYZliang
Copy link

当发送的消息包含#时,#后面的所有内容会被吞掉
如果内容开头是#,则直接报错 "The text must be a string."
本意输出一个#,就会出现以上错误。
image
如果内容是123#456#789,通知端只能收到123,#后全部没了
必须发送%23,即把#编码后,才能发送正常
image

@XYZliang XYZliang changed the title 希望API接口能对内容进行编码 #号后内容被吞 Jan 27, 2022
@XYZliang
Copy link
Author

XYZliang commented Jan 27, 2022

如果对text内容强制编码的话,虽然#号的问题能解决,但是换行需要用的0%A也会被编码,导致通知里得到的也是0%A。
image
image
如果不编码,那么#号后的内容又没了
image

@easychen
Copy link
Owner

在强制编码的情况下,换行本身就会被替换为%0A,不用手工替换了。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants