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 _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
