From: Ulrich Drepper <drepper@redhat.com>
To: libc-hacker@sourceware.org
Subject: Re: [PATCH] Don't reject name server due to empty answer
Date: Wed, 17 Mar 2010 14:20:00 -0000 [thread overview]
Message-ID: <4BA0E52C.8060701@redhat.com> (raw)
In-Reply-To: <m3tysgyymt.fsf@hase.home>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/16/2010 10:17 AM, Andreas Schwab wrote:
> The resolver rejects a name server when it responds with an empty reply
> (both AA and RA flags cleared) like this:
This code was added for a reason:
https://bugzilla.redhat.com/show_bug.cgi?id=162625
Why should this be reverted? Yes, the TCP code should likely be fixed
up as well but that's a different story.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkug5SwACgkQ2ijCOnn/RHRvPACeKkzg3lXy7czgzn7M24IoEAdu
6iIAn3THopqQmmooHpKZVvjeGaklSqqE
=5G4u
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-03-17 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 17:17 Andreas Schwab
2010-03-17 14:20 ` Ulrich Drepper [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA0E52C.8060701@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).