From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: git daemon directory munging?
Date: Sun, 04 Jun 2006 16:10:32 -0700 [thread overview]
Message-ID: <44836868.1050700@zytor.com> (raw)
In-Reply-To: <7vverhcu5n.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>
> Adding host like HTTP does with Host: header makes sense but I
> think the accept side can usually tell what the port it accepted
> the connection to is.
>
Yes, but that requires that each hostname has a separate IP address
and/or port number (and SRV records in DNS, which not all platforms pay
attention to.)
Now, if the hostname is passed in like this, it needs to be carefully
canonicalized, and there needs to be provisions for wildcard matches.
-hpa
next prev parent reply other threads:[~2006-06-04 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 0:13 git daemon directory munging? Jon Loeliger
2006-06-04 0:42 ` Linus Torvalds
2006-06-04 6:27 ` Junio C Hamano
2006-06-04 23:10 ` H. Peter Anvin [this message]
2006-06-04 23:08 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 2:10 Jon Loeliger
2006-06-05 2:59 ` H. Peter Anvin
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=44836868.1050700@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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 NNTP newsgroup(s).