-
Notifications
You must be signed in to change notification settings - Fork 75
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
Update ares_query_txt_result_chunk to return bytes rather than str #160
base: master
Are you sure you want to change the base?
Conversation
The RFC1035 specification says that TXT records are allowed to contain <character-string> data made of arbitrary binary data, but right now aiodns is parsing it as a str, and therefore will stop on a null byte, this PR fixes this
I think we need to apply the same to |
I’m on holidays for a few days but I can do it when I come back
… On 11 Aug 2021, at 09:52, Saúl Ibarra Corretgé ***@***.***> wrote:
I think we need to apply the same to ares_query_txt_result, don't we? Also, I wonder why the GH action with the tests didn't run...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Sure thing, no rush, and thanks for helping out with this! |
ares_query_txt_result returns bytes so that it stays coherent
@saghul I guess that now that both return bytes it should work as expected |
Free the hostent in both cases
Reorder to be consistent with initial code
It seems that the https://mxtoolbox.com/SuperTool.aspx?action=txt%3atxt-non-ascii.dns-test.hmnid.ru&run=toolpage |
Also the
|
The RFC1035 specification says that TXT records are allowed to contain data made of arbitrary binary data, but right now aiodns is parsing it as a str, and therefore will stop on a null byte, this PR fixes this