- From: Martin Nilsson <nilsson@opera.com>
- Date: Sun, 15 Jun 2014 22:03:27 +0200
- To: ietf-http-wg@w3.org
On Fri, 13 Jun 2014 20:58:52 +0200, Mark Nottingham <mnot@mnot.net> wrote: > So far, the proxy-related work that seems to have some level of > consensus to continue upon has been: > > ## HTTP Proxy Problems > > IIRC Julian volunteered to edit this if we choose to adopt it. Julian, > is that still the case? > > Do people support adopting this as a WG Draft (with a target of > Informational)? If not, please explain why. I approve of this, and when Julian and I spoke in New York I promised to support him with any information he needs from me. > ## Autoproxy.pac format > > There was also significant interest in standardising the autoproxy.pac > format, possibly extending or refining it along the way. However, we > haven’t seen any drafts or discussion of that. Is anyone planning to > propose something here? Richard Wheeldon and I discussed different methods to try to find out what the current use cases are, scanning existing autoproxy.pac files and looking over the code for the sandbox they are executed in. I would say that other aspects of proxies have higher priority, at least for me right now. On the other hand I fear that this will always be the case for everyone, which is probably why autoproxy.pac has such an open API right now. > ## UX > > Another thing mentioned in the London DTM was the need for UX. We said > there (and I still agree) that this is *not* the venue for that > discussion, but it needs to happen somewhere, and it’s likely to block > what we do. Is anyone aware of a place where that is happening (W3C > seems like an obvious possibility, but I haven’t heard anything from > them)? UX for what? We did have UX resources working on the explicit authenticated proxy prototype, but that is just one use case, that even might end up not being relevant for anyone. /Martin Nilsson -- Using Opera's mail client: http://www.opera.com/mail/
Received on Sunday, 15 June 2014 20:03:58 UTC