From: "Daniel Berlin" <dberlin@dberlin.org>
To: NightStrike <nightstrike@gmail.com>
Cc: "Ian Lance Taylor" <iant@google.com>, overseers@gcc.gnu.org
Subject: Re: [NightStrike <nightstrike@gmail.com>] SVN access over https (SSL)
Date: Sat, 29 Sep 2007 05:26:00 -0000 [thread overview]
Message-ID: <4aca3dc20709282226j66acf6c0w4ba70712d8edf306@mail.gmail.com> (raw)
In-Reply-To: <b609cb3b0709282222k6aae90aat1029942ccc30b7fb@mail.gmail.com>
On 9/29/07, NightStrike <nightstrike@gmail.com> wrote:
> On 9/28/07, Daniel Berlin <dberlin@dberlin.org> wrote:
> > Most people who proxy https proxy http as well.
>
> proxy https is much more compatible with picky proxies than http when
> dealing with svn.
>
Being an svn developer who has had to debug proxy problems, i'd
actually say exactly the exact opposite.
Most HTTPS proxies fuck it up more often than HTTP proxies.
In any case, if someone wants to buy a cert for gcc.gnu.org, i'll set
up https read-only access.
But honestly, I have real trouble seeing that it is truly that useful
when we have http access.
--Dan
next prev parent reply other threads:[~2007-09-29 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 0:36 Ian Lance Taylor
2007-09-29 0:41 ` Daniel Berlin
2007-09-29 1:27 ` Ian Lance Taylor
2007-09-29 2:00 ` Daniel Berlin
2007-09-29 5:22 ` NightStrike
2007-09-29 5:26 ` Daniel Berlin [this message]
[not found] ` <b609cb3b0709290503l41bd9adcifdde549e2a895b4f@mail.gmail.com>
2007-09-29 14:02 ` Daniel Berlin
2007-09-30 5:09 ` NightStrike
2007-09-30 20:22 ` Daniel Berlin
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=4aca3dc20709282226j66acf6c0w4ba70712d8edf306@mail.gmail.com \
--to=dberlin@dberlin.org \
--cc=iant@google.com \
--cc=nightstrike@gmail.com \
--cc=overseers@gcc.gnu.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).