  Some proxy needs  From: Nicolas Mailhot
<nicolas.mailhot@laposte.net> Date: Sun, 8 Apr 2012 14:14:15
+0200 Message-ID:
<3dfc2c17927267e41710084836183f71.squirrel@arekh.dyndns.org> To:
ietf-http-wg@w3.org I'll attempt a quick summary of what's been
written on the list those past weeks  A proxy needs:  1.
discoverability, to handle network guests (right now taken care
of wpad+pac though a lot of clients do not handle those, and
they are not really satisfactory I guess). Automated
discoverability is not the same thing as applying those blindly
in the web client behind the user back. The web client is free
to try a direct connection anyway, but if it fails it should
notify the user of a proxy presence and have it accept it, or
not. Right now no discoverability means settings are copied
blindly by users from one web client to another, and I fail to
see how that improves security.  2. a way to signal the web
client a specific URL access (any access at any time) needs
proxy authorization, and where this authorizat