[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [patch #9654] getaddrinfo failed when addr has a upper char
|
From: |
Simon Goldschmidt |
|
Subject: |
[lwip-devel] [patch #9654] getaddrinfo failed when addr has a upper character |
|
Date: |
Wed, 13 Jun 2018 06:24:07 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Follow-up Comment #4, patch #9654 (project lwip):
> Many developer not known "dns 0x20 bit encoding". So it will take many time
on 202 error code.
No, developers don't need to know about "dns 0x20 bit encoding", this is a dns
internal. It is meant to make dns a bit more secure to be able to reject
spoofed response packets where the 0x20 bit does not match.
However, we do not use this encoding at all. We just map the first request
through to the net. I'm not 100% sure though whether the standard requires
preserving the case in a response, that's why I asked which resolver you are
using.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/patch/?9654>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/