From: Jeff King <peff@peff•net>
To: Yi EungJun <semtlenori@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Git + SFC Status Update
Date: Thu, 16 Apr 2015 05:31:26 -0400 [thread overview]
Message-ID: <20150416093126.GB18135@peff.net> (raw)
In-Reply-To: <1429173474310-7628850.post@n2.nabble.com>
On Thu, Apr 16, 2015 at 01:37:54AM -0700, Yi EungJun wrote:
> > - Written policy: https://git-scm.com/trademark
>
> My browser shows an "Untrusted Connection" page when click the link.
>
> Does git-scm have no TLS certificate?
Hmm, you're right. It has a *.herokuapp.com cert. That's fine for
hitting https://git-scm.herokuapp.com, but obviously not when you use
the custom domain. I think I manually accepted the cert long ago and
forgot about it.
Looks like somebody opened
https://github.com/git/git-scm.com/issues/489
but nobody has dealt with it. I have no idea what the recommended setup
is for dealing with TLS and custom domains on Heroku.
-Peff
prev parent reply other threads:[~2015-04-16 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 11:56 Git + SFC Status Update Jeff King
2015-04-13 15:24 ` Michael J Gruber
2015-04-14 19:00 ` Dave Borowitz
2015-04-14 19:30 ` Junio C Hamano
2015-04-14 23:54 ` Jeff King
2015-04-15 15:55 ` Dave Borowitz
2015-04-15 16:07 ` Junio C Hamano
2015-04-16 8:37 ` Yi EungJun
2015-04-16 9:31 ` Jeff King [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=20150416093126.GB18135@peff.net \
--to=peff@peff$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=semtlenori@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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