Re: Alt-Svc + Proxy Pac
Ryan Hamilton <rch@google.com> Fri, 03 April 2015 21:21 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A75521A8860 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Apr 2015 14:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.389
X-Spam-Level:
X-Spam-Status: No, score=-6.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xShmSysF2Yp3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Apr 2015 14:21:45 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF3E81A8775 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 3 Apr 2015 14:21:45 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Ye8yy-00081w-Ea for ietf-http-wg-dist@listhub.w3.org; Fri, 03 Apr 2015 21:18:28 +0000
Resent-Date: Fri, 03 Apr 2015 21:18:28 +0000
Resent-Message-Id: <E1Ye8yy-00081w-Ea@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <rch@google.com>) id 1Ye8yu-00081B-9S for ietf-http-wg@listhub.w3.org; Fri, 03 Apr 2015 21:18:24 +0000
Received: from mail-yk0-f179.google.com ([209.85.160.179]) by maggie.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <rch@google.com>) id 1Ye8yt-0001T5-6M for ietf-http-wg@w3.org; Fri, 03 Apr 2015 21:18:24 +0000
Received: by ykft189 with SMTP id t189so10148802ykf.1 for <ietf-http-wg@w3.org>; Fri, 03 Apr 2015 14:17:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uCEZly8lAeB/DhzknlwUJ+oEpPctjIefWxZTuI67BUc=; b=C5G/WTyuQnXj3WQXqXKEXojk17AudLJ2g7dbe+H98CkMyEbXBCAoZSOAWgbSZN1mz0 fAjMgu6MJcNLeXRCPZPhYtSFjSQDuR2ptj3HSCNGUUav+sqJwOss5HCTKDwO1l02qrd/ V0ODd19TEGDmtMGIXm6eo01BShywfkGN0LmVsDVi1aCu9qqmV0iItRAwVC7nG99CK0df lfQLFSOYeCZayqLGM2vYfJFXMOzdH9UdNgIBJAJ6gmnRx9uyrI5y9PGHSvJHljETn+CA sb73AidfIa6uMKiP6coZ3kX02Mgref2k30x35OeRcIalH3hxqD0+xN7NYL4S6S3KSQXS NdHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uCEZly8lAeB/DhzknlwUJ+oEpPctjIefWxZTuI67BUc=; b=C9mJK3jwHwPg0Fkpk4oxAi3YhwE+r0OUwxloz5xJeB+tS7ItHDUvzq134JNlTikDiJ WAIrB0jWHh9Wra/900RldUL2axIN/RzKBS95lxKMTrRvWDEWXzwZJwgqG87eHMjs4yGq osuk0WwGCFWrMLPbsNqM8/JLyxtrUIiG/gx1qsgaiDzBTTMigv2EdexdwVaDqjnHrkts HySuxrA8L/IFLFsLpGNVmky/Hw5fcFJIPlN1xaKY++FWyCAvtbCQPr5fMKj2G0xRYO72 M+GEV9XrUxUVP8KVcry0Rg9uj07i8WgdrrYN5feFKvVh2ZtwnhYK4JKphzeVx8j6z6wF 5Xuw==
X-Gm-Message-State: ALoCoQmU4IUVHULPkyI7BFs6lqnANHGycy85TCBriVmpODCONJefOnMjckUGEHw2pYsCCKEwuugd
MIME-Version: 1.0
X-Received: by 10.52.94.6 with SMTP id cy6mr2428150vdb.48.1428095876857; Fri, 03 Apr 2015 14:17:56 -0700 (PDT)
Received: by 10.52.169.202 with HTTP; Fri, 3 Apr 2015 14:17:56 -0700 (PDT)
In-Reply-To: <CAOdDvNq9cp_bAYy_F_1nA0cHNKfxWVEi5uqmDoZiGoyxjtnvZA@mail.gmail.com>
References: <CAJ_4DfS5J0k-G_fY46R=8jJDbppC8EfvAmLCaeccPFudOfFM0g@mail.gmail.com> <CABkgnnWXR7H1oZWLLT7ZhoOtPZjVVDnYaqTYACBkoVQ2scrKJA@mail.gmail.com> <CAJ_4DfTBn=QZy=219FDsT-+bHyK-9qfcUfgdxAJFZwN=-JUpNQ@mail.gmail.com> <CAOdDvNq9cp_bAYy_F_1nA0cHNKfxWVEi5uqmDoZiGoyxjtnvZA@mail.gmail.com>
Date: Fri, 03 Apr 2015 14:17:56 -0700
Message-ID: <CAJ_4DfR-kpiGmdDQXRG85E46jjNtYP82L7NCqWk8gXHy4=wYTw@mail.gmail.com>
From: Ryan Hamilton <rch@google.com>
To: Patrick McManus <mcmanus@ducksong.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="20cf307abe9f7212f30512d87b5f"
Received-SPF: pass client-ip=209.85.160.179; envelope-from=rch@google.com; helo=mail-yk0-f179.google.com
X-W3C-Hub-Spam-Status: No, score=-4.4
X-W3C-Hub-Spam-Report: AWL=-1.583, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1Ye8yt-0001T5-6M 1dfcf6a7954c155da040ad6ba384f2e2
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Alt-Svc + Proxy Pac
Archived-At: <http://www.w3.org/mid/CAJ_4DfR-kpiGmdDQXRG85E46jjNtYP82L7NCqWk8gXHy4=wYTw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29246
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On Fri, Apr 3, 2015 at 2:04 PM, Patrick McManus <mcmanus@ducksong.com> wrote: > > On Fri, Apr 3, 2015 at 4:50 PM, Ryan Hamilton <rch@google.com> wrote: > >> Consider the following scenario. There are two servers, >> internal.example.com and external.example.com. Inside the enterprise >> access to resources outside the firewall must go through a proxy, whereas >> resource inside the firewall can go direct. That would lead to a .pac file >> like: >> >> function FindProxyForURL(url, host) { >> >> if (host == "internal.example.com") { >> return "DIRECT"; >> } >> return "PROXY proxy.example.com"; >> } >> >> >> If Alt-Svc for internal says, "Alt-Svc: h2="external.exmple.com:443", >> then the proxy will say, "Sure, go direct to >> http://internal.example.com/" but then the browser will connect to >> external.example.com:443 and will avoid the proxy and the request will >> hang. This seems a bit unfortunate, but it's not clear that the alternative >> is much better, so I'm happy to do this, if that's the consensus of the >> group. >> > > > The browser is supposed to validate the alternate service (among other > things by checking that it has a cert valid for the origin) before using it > and fall back if it is unavailable. So it seems that > external.example.com:443 could not be validated in your example and if > perhaps that validation were stale, it should get automagically cleaned up. > Agreed! When I said, "the request will hang", I meant to say, "the connection will hang". You're totally right that this won't be a user facing problem. We won't use the alternative-service but it's not the end of the world. I would be very cautious about ever changing url based on alt-svc.. alt-svc > does not change origins or urls. If it did, it would get very hard to > reason about. but supplying the alt information explicitly seems a lot more > interesting. > Agreed. > Somebody should really write up a I-D for a modern PAC (that could be me, > but realistically a lot of other things would have to come off the todo > list first.) > SGTM. Especially the part about you doing the work :>
- Alt-Svc + Proxy Pac Ryan Hamilton
- Re: Alt-Svc + Proxy Pac Martin Thomson
- Re: Alt-Svc + Proxy Pac Martin Thomson
- Re: Alt-Svc + Proxy Pac Francesco Chemolli
- Re: Alt-Svc + Proxy Pac Patrick McManus
- Re: Alt-Svc + Proxy Pac Ryan Hamilton
- Re: Alt-Svc + Proxy Pac Ryan Hamilton
- Re: Alt-Svc + Proxy Pac Ryan Hamilton
- Re: Alt-Svc + Proxy Pac Patrick McManus
- Re: Alt-Svc + Proxy Pac Ryan Hamilton
- Re: Alt-Svc + Proxy Pac Martin Thomson