git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Kyle J. McKay" <mackyle@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: git_inetd_server: run git-http-backend using inetd
Date: Thu, 17 Jul 2014 15:10:56 -0700	[thread overview]
Message-ID: <20140717221056.GO12427@google.com> (raw)
In-Reply-To: <43923BC7-08AF-4900-AC5E-B2F0FE7CD5AC@gmail.com>

Hi,

Kyle J. McKay wrote:

> When I then try to fetch using a "git://host/..." URL where "host"
> is an mDNS host name, the 0010 patch causes git to attempt to lookup
> a DNS SRV record on the non-mDNS regular DNS service (a violation of
> RFC 6762 [4] section 22) and this is what has to time out before the
> real fetch can start.

That patch uses res_query from libresolv to do the lookup.  It doesn't
know what DNS server to use and relies on system libraries to get it
right.

It was added to respond to a feature request within Debian but it is
intended to eventually go upstream.  I'm glad you found this issue
before that could happen. :)

Should git automatically disable the SRV lookups when it sees one of
the six domains named in RFC6762, or is there some system library call
that can use mDNS when appropriate automatically (or get partway there
without having to hard-code the domains)?

Thanks,
Jonathan

  reply	other threads:[~2014-07-17 22:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 21:28 git_inetd_server: run git-http-backend using inetd Kyle J. McKay
2014-07-17 22:10 ` Jonathan Nieder [this message]
2014-07-17 23:38   ` Kyle J. McKay
2014-07-18  2:22     ` Jonathan Nieder
2014-07-18  6:48       ` Kyle J. McKay
2014-07-18 17:16         ` Jonathan Nieder
2014-07-19  0:08           ` Kyle J. McKay
2014-07-19  0:19             ` Jonathan Nieder
2014-07-19  1:54               ` Kyle J. McKay
2014-07-19  6:21   ` Torsten Bögershausen
2014-07-19 17:06     ` Jonathan Nieder
2014-07-20  6:10       ` Torsten Bögershausen
2014-07-20 15:25         ` Torsten Bögershausen

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=20140717221056.GO12427@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mackyle@gmail.com \
    /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 NNTP newsgroup(s).