From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Proxy servers per protocol and domain
Date: Mon, 7 Jul 2014 09:29:38 +0100 [thread overview]
Message-ID: <20140707082938.GA16676@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140605003023.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
On Sat, Jul 05, 2014 at 12:30:23AM -0400, Karl Dahlke wrote:
> Ok, you got it, at least my first try.
Thanks. According to my tests (using db4 to verify the proxy is being changed)
this appears to be working correctly.
Note that I've only tested http and https so far as I don't know the details
for our ftp proxy.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-07-07 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 4:30 Karl Dahlke
2014-07-07 8:29 ` Adam Thompson [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=20140707082938.GA16676@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).