Fwd: Header addition with HTTP 2.0

Bence Béky <bnc@chromium.org> Tue, 31 March 2015 20:08 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 722EB1ACC7F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 31 Mar 2015 13:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.09
X-Spam-Level:
X-Spam-Status: No, score=-6.09 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, MIME_8BIT_HEADER=0.3, 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 PDPgFFk5Ck7s for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 31 Mar 2015 13:07:59 -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 5442A1A702D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 31 Mar 2015 13:07:59 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Yd2Pm-0006j7-95 for ietf-http-wg-dist@listhub.w3.org; Tue, 31 Mar 2015 20:05:34 +0000
Resent-Date: Tue, 31 Mar 2015 20:05:34 +0000
Resent-Message-Id: <E1Yd2Pm-0006j7-95@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <bnc@google.com>) id 1Yd2Pf-0006h1-67 for ietf-http-wg@listhub.w3.org; Tue, 31 Mar 2015 20:05:27 +0000
Received: from mail-qc0-f179.google.com ([209.85.216.179]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <bnc@google.com>) id 1Yd2Pe-00017x-4K for ietf-http-wg@w3.org; Tue, 31 Mar 2015 20:05:27 +0000
Received: by qcay5 with SMTP id y5so23710457qca.1 for <ietf-http-wg@w3.org>; Tue, 31 Mar 2015 13:05:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=1y5sg5JwH/gSiQf+Cuc0/OVXdBOtGLEzr/Bz2JooZAs=; b=GLV+oXai6P8ICrB85S0B8ooyLlVRzr2GqLCujKByT1ls2bHYNvT+0x4FI7YSnJya2c kHb2vZAKIoa5O6RG8CxH74UhmbTuK+RO/LqrylX0saO7h6jB9b2lwVuhvjx0yDtaTeac kdGV4QmQACLUs1/zVlnveThAeQ0p5CifBZEDvOpsBAKx/guqOwDVrbVgrrDF2uMSKbVi BQoYpLGZpimT9VRVre6mXvPejvU6U0NZ/mp5XqcaVTKWP3FovOBpIYdni+HKcBZA0Oh/ MbfeherJFyRxS3hpoLCmDDkXBl8jhhJ2zohGr/vgE/fQylSl8Udfikyu+IqVaps+jUDX 4AXg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=1y5sg5JwH/gSiQf+Cuc0/OVXdBOtGLEzr/Bz2JooZAs=; b=iJzMVztrXDrjmxq6u6Ju2lD15xZnO/Lrddjtjx+7TauF/anb1U4Alv8FlJMbIhzyNl srr4gcpiLGR7FBxD4SKD5+Gmmm1FsvYBFS4Sb/7kbnRZD6vJvdIMjVOwb7+8Jw2jRJyA WPeKaQMmMINXcjgEIQioR4pKptdxvzysj+q9k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-type; bh=1y5sg5JwH/gSiQf+Cuc0/OVXdBOtGLEzr/Bz2JooZAs=; b=LeN4iYg6vt5mqNr7BKZysEmcu5ccRWpjDdQsYpKl3WEdA1wWiPGjhZvP9cPHSi8yk/ hWbg+h88lrzQWpa+hvdw/zyyXN1wEqpuNUCQKM0pFz8OE6TRdGhdearNplZgdPOMtR0D D3KInegNx23ihqWjAqbrbFY18NrWfbul4QMKuYMnXkpJOifx7lPKSr9TbAovYLe7klu1 Otiu4U6fKLAN6Un/NALcOGy2yFoDMWyQBXaXYAU3UQl26YXbULBAIYnz9n3vwP7vKsvh GbJ5s6m10ljrjSmlf5WqMxsrrpTZ8BHmes5efS2J76uNYR8y2I1luKzt2XG1wy3unp2p p18A==
X-Gm-Message-State: ALoCoQk23DwPkJLiItMooLNpNpTYYAkNSnDnr9XxWWKEKoN+rAc7OAUQE/AJYMeylY17Cg1TYCLW
X-Received: by 10.55.43.14 with SMTP id r14mr82006430qkh.35.1427832299808; Tue, 31 Mar 2015 13:04:59 -0700 (PDT)
MIME-Version: 1.0
Sender: bnc@google.com
Received: by 10.229.178.6 with HTTP; Tue, 31 Mar 2015 13:04:39 -0700 (PDT)
In-Reply-To: <CACMu3toR56=u+XG1qtGD=HP9Sy32rd_23QNRMzX3+XwucFYxhA@mail.gmail.com>
References: <CAKwtvnAtuF-X3pgbgLe7VAdnMd4+Yy1EeZLaHgyXXTnZRBgFZw@mail.gmail.com> <CACMu3toR56=u+XG1qtGD=HP9Sy32rd_23QNRMzX3+XwucFYxhA@mail.gmail.com>
From: Bence Béky <bnc@chromium.org>
Date: Tue, 31 Mar 2015 16:04:39 -0400
X-Google-Sender-Auth: mqm-PSpwwZVEACr5tFcjxnDj2Kk
Message-ID: <CACMu3toheWOPAmEFyuM-uH1NZkL-g2Tw-CuFbv_5fAOG8tyY-Q@mail.gmail.com>
To: HTTP <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.216.179; envelope-from=bnc@google.com; helo=mail-qc0-f179.google.com
X-W3C-Hub-Spam-Status: No, score=-5.3
X-W3C-Hub-Spam-Report: AWL=-0.543, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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: lisa.w3.org 1Yd2Pe-00017x-4K 8da8b5ffaf3227aaf3ca0be1c972eca8
X-Original-To: ietf-http-wg@w3.org
Subject: Fwd: Header addition with HTTP 2.0
Archived-At: <http://www.w3.org/mid/CACMu3toheWOPAmEFyuM-uH1NZkL-g2Tw-CuFbv_5fAOG8tyY-Q@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29133
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>

[re-posting from the right address]

Hi,

On Mon, Mar 30, 2015 at 5:34 PM, Vimala Tadepalli <vimla.c@gmail.com> wrote:
> In HTTP 2.0, can i do this?
> If a header is added at firewall, client and server dynamic tables might go
> out of sync. Will it cause any issues?

Good question.  My understanding is that the firewall is supposed to
re-encode the header.  That is, it should maintain a dynamic table on
its connection with the client that stays in sync with that of the
client, decode the header block using this dynamic table, and
re-encode it towards the server using a context that is in sync with
the server.

Cheers,

Bence