edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  A couple of feature requests
Date: Fri, 04 Jul 2014 09:27:44 -0400	[thread overview]
Message-ID: <20140604092744.eklhad@comcast.net> (raw)

In much of edbrowse, and even in some of life,
I try not to let the best be the enemy of the good.
The best would be the javascript pac file approach, and honestly I think
we should implement that in the near future.
I don't think it would be hard, given that we have javascript suppport,
and the underlying js function isn't likely to be complicated.
But sooner than that, perhaps we should get some noprox exceptions running.
That's even easier, and it's a stepping stone,
determining the proxy at connect time rather than init time.
And we must remember that sometimes we run edbrowse with js turned off,
perhaps in general or perhaps per site.
In that case the js context isn't even there.
We don't have the option of running the pac file.
I think some folks will want a little more proxy control even with js turned off.
Then, when js is enabled, and if there is a pac file,
we can support that.
So I propose starting with some proxy exceptions in the config file,
and seeing where that leads.

Karl Dahlke

             reply	other threads:[~2014-07-04 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04 13:27 Karl Dahlke [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2014-07-04  6:50 ` Chris Brannon
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=20140604092744.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.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).