edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] A couple of feature requests
Date: Fri, 4 Jul 2014 13:45:16 +0100	[thread overview]
Message-ID: <20140704124516.GC7896@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87d2dm5u59.fsf@mushroom.PK5001Z>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

On Thu, Jul 03, 2014 at 08:39:14AM -0700, Chris Brannon wrote:
> Karl Dahlke <eklhad@comcast.net> writes:
> 
> > Can you specify proxy exceptions within curl?
> 
> Nope.
> This will be a fun can of worms.
> In corporate settings, the proxy you use may depends on the
> URL you're trying to fetch.
> See http://en.wikipedia.org/wiki/Proxy_auto-config
> It's going to be more complicated than just supporting exceptions.

Whereas full PAC file support would be nice (and I'd like to see it in the
future), at my $large_company at the moment I think I only need a sufficiently
useful proxy selection mechanism. At the end of the day,
if we can get a sufficiently powerful mechanism in place then we can do the js
bindings to it.

That being said, I'm all in favour of designing the mechanism properly so that
supporting PAC files is just a case of a few js bindings.
Also, doing it this way we can support both hard-coded and PAC file based proxy selection, which would be really useful in my opinion.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-07-04 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03  9:19 Karl Dahlke
2014-07-03 14:54 ` Adam Thompson
2014-07-03 15:39 ` Chris Brannon
2014-07-04 12:45   ` Adam Thompson [this message]
2014-07-04  6:50 ` Chris Brannon
  -- strict thread matches above, loose matches on Subject: below --
2014-07-04 13:27 Karl Dahlke
2014-07-02 19:44 Adam Thompson

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=20140704124516.GC7896@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chris@the-brannons.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).