Re: [hybi] a question about the redirect of websocket
Takeshi Yoshino <tyoshino@google.com> Mon, 20 February 2012 06:14 UTC
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7A921F85D7 for <hybi@ietfa.amsl.com>; Sun, 19 Feb 2012 22:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.676
X-Spam-Level:
X-Spam-Status: No, score=-102.676 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_41=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HgjlAobedzsb for <hybi@ietfa.amsl.com>; Sun, 19 Feb 2012 22:14:00 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id B7A8021F84B5 for <hybi@ietf.org>; Sun, 19 Feb 2012 22:13:57 -0800 (PST)
Received: by yhkk25 with SMTP id k25so2816636yhk.31 for <hybi@ietf.org>; Sun, 19 Feb 2012 22:13:57 -0800 (PST)
Received-SPF: pass (google.com: domain of tyoshino@google.com designates 10.236.78.231 as permitted sender) client-ip=10.236.78.231;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tyoshino@google.com designates 10.236.78.231 as permitted sender) smtp.mail=tyoshino@google.com; dkim=pass header.i=tyoshino@google.com
Received: from mr.google.com ([10.236.78.231]) by 10.236.78.231 with SMTP id g67mr25872391yhe.117.1329718437413 (num_hops = 1); Sun, 19 Feb 2012 22:13:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=EmWGB0mu3SUteE/RKLTOEsF/nxeiGD8BmJlzOteTIR8=; b=GXiBabss7uXHfeZHmN/pnph5mC5bSno0f6bR2y4QwT2ox9esG1zmxUU2TAPv0zuirJ z/xKJW5oJ2TnzAA1kwzSmwlnedn16R5wr9ENQtPIn2Z0QernZJgan9DHOKsfGcu7lzIL vUC8MqvFG+n44ckNu+xuKMYxVPD+M8Ks1QV/k=
Received: by 10.236.78.231 with SMTP id g67mr19881869yhe.117.1329718437368; Sun, 19 Feb 2012 22:13:57 -0800 (PST)
Received: by 10.236.78.231 with SMTP id g67mr19881858yhe.117.1329718437284; Sun, 19 Feb 2012 22:13:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.236.35 with HTTP; Sun, 19 Feb 2012 22:13:37 -0800 (PST)
In-Reply-To: <CAJoFd65uEwm-3V-FtBZngctXvd4jfX-2pthVw==yo9+mJyLhKA@mail.gmail.com>
References: <CAJoFd65uEwm-3V-FtBZngctXvd4jfX-2pthVw==yo9+mJyLhKA@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Mon, 20 Feb 2012 15:13:37 +0900
Message-ID: <CAH9hSJZPOuO0fGzfkiFEF6=ghTLMnfiQ5txqR+rwC_eZHCiRMQ@mail.gmail.com>
To: juan li <ruoqiu.lee@gmail.com>
Content-Type: multipart/alternative; boundary="20cf300fb1a51b0a2804b95f3346"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkg8ae8NF/0VOQiX0ziWI8tE+mTXn6C7SzL2DoeIMLpFrDY0tEAkVE8RQP1+2s25qtgTyZ19eFN+bb/hc5o4Yw0OVADgEdmbkd8nB+80M8CmKhvOk6UoLB9Q6jsiGIzbJ47Kz6h
Cc: hybi@ietf.org
Subject: Re: [hybi] a question about the redirect of websocket
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2012 06:14:01 -0000
On Thu, Feb 16, 2012 at 00:23, juan li <ruoqiu.lee@gmail.com> wrote: snip. > process the data frames". How to do this(A server has completed the > handshake and then passes the connection to another server)? > I think "pass the connection" in the sentence means forwarding everything following the opening handshake to backends (possibly converted into some in-data-center protocol) and forwarding data returned from backends to the client.