Re: [PATCH v4] BUG/MINOR: dns: allow 63 char in hostname

2020-01-28 Thread Baptiste
On Tue, Jan 28, 2020 at 12:19 AM Miroslav Zagorac wrote: > On 01/28/2020 12:02 AM, Baptiste wrote: > > On Sun, Jan 26, 2020 at 7:53 PM William Dauchy > wrote: > > > >> hostname were limited to 62 char, which is not RFC1035 compliant; > >> - the parsing loop should stop when above max label char

Re: [PATCH v4] BUG/MINOR: dns: allow 63 char in hostname

2020-01-28 Thread Willy Tarreau
On Tue, Jan 28, 2020 at 12:02:18AM +0100, Baptiste wrote: > On Sun, Jan 26, 2020 at 7:53 PM William Dauchy wrote: > > > hostname were limited to 62 char, which is not RFC1035 compliant; > > - the parsing loop should stop when above max label char > > - fix len label test where d[i] was wrongly

Re: [PATCH v4] BUG/MINOR: dns: allow 63 char in hostname

2020-01-27 Thread Miroslav Zagorac
On 01/28/2020 12:02 AM, Baptiste wrote: On Sun, Jan 26, 2020 at 7:53 PM William Dauchy wrote: hostname were limited to 62 char, which is not RFC1035 compliant; - the parsing loop should stop when above max label char - fix len label test where d[i] was wrongly used - simplify the whole

Re: [PATCH v4] BUG/MINOR: dns: allow 63 char in hostname

2020-01-27 Thread Baptiste
On Sun, Jan 26, 2020 at 7:53 PM William Dauchy wrote: > hostname were limited to 62 char, which is not RFC1035 compliant; > - the parsing loop should stop when above max label char > - fix len label test where d[i] was wrongly used > - simplify the whole function to avoid using two extra char*

Re: [PATCH v4] BUG/MINOR: dns: allow 63 char in hostname

2020-01-26 Thread Tim Düsterhus
William, Am 26.01.20 um 19:52 schrieb William Dauchy: > hostname were limited to 62 char, which is not RFC1035 compliant; > - the parsing loop should stop when above max label char > - fix len label test where d[i] was wrongly used > - simplify the whole function to avoid using two extra char*

[PATCH v4] BUG/MINOR: dns: allow 63 char in hostname

2020-01-26 Thread William Dauchy
hostname were limited to 62 char, which is not RFC1035 compliant; - the parsing loop should stop when above max label char - fix len label test where d[i] was wrongly used - simplify the whole function to avoid using two extra char* variable this should fix github issue #387 Signed-off-by: