IETF Logo Mail Archive

Re: [hybi] Multiple connections serialization and proxies

Wellington Fernando de Macedo <wfernandom2004@gmail.com> Thu, 22 April 2010 19:11 UTC

Return-Path: <wfernandom2004@gmail.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80EC828C206 for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 12:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.066
X-Spam-Level:
X-Spam-Status: No, score=0.066 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jt3baGzAPoDX for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 12:11:47 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 3260B3A69D5 for <hybi@ietf.org>; Thu, 22 Apr 2010 11:50:23 -0700 (PDT)
Received: by vws1 with SMTP id 1so223013vws.31 for <hybi@ietf.org>; Thu, 22 Apr 2010 11:50:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=roU7B5dGkIs1PZ1JhjynxL47k1hxatVuzRC8gREG0ck=; b=Iwu72iPVaBQXFrTn7dUGZ75Lcvz8XENBLotKb51BHXrF0vbwpeh/WXsuVr47Imaz1u ar54k9iRcFvjLbSdGq5GBQYoFGFkXUhP8mb9CuZYOuHmo61c1aMJHLss81qbdQSlT4QY DzMlUrwBZ/76YeOl18ZEquC5kWYQiaF62sM34=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=vX4K+IN3rLBvWYbGT3ykQYxaTbTXVuoBcks+FIRFeZrR5Me9r9H1meesEPLYccMeWk 7tp6yzhztUkvwAQB0VIIjjeq13QXvamDJ59TsJy7tZvnukKoK6EJuk5xfDJnFCHXWJVi wx+VflaaSwWnF1nvjJau8Ri0vwZu4zFxq8BBo=
Received: by 10.229.248.137 with SMTP id mg9mr1134137qcb.33.1271962209304; Thu, 22 Apr 2010 11:50:09 -0700 (PDT)
Received: from [192.168.1.21] (www.simucad.dep.ufscar.br [200.136.228.238]) by mx.google.com with ESMTPS id f5sm136573qcg.2.2010.04.22.11.50.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 22 Apr 2010 11:50:08 -0700 (PDT)
Message-ID: <4BD09A2C.6060506@gmail.com>
Date: Thu, 22 Apr 2010 15:49:16 -0300
From: Wellington Fernando de Macedo <wfernandom2004@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: hybi@ietf.org
References: <4BCF4932.8040303@gmail.com>
In-Reply-To: <4BCF4932.8040303@gmail.com>
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] Multiple connections serialization and proxies
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 22 Apr 2010 19:11:48 -0000

Hi again,

We (Ian, Christian Biesinger and me) have talked about this issue. We've decided that, when under proxies, Mozilla's implementation will serialize the connections using the host names.

Ian, can you update the spec accordingly, please?

Wellington.

Em 21/4/2010 15:51, Wellington Fernando de Macedo escreveu:
Hi,

A question has been raised in the Mozilla implementation. The spec states:

 
   1.   If the user agent already has a WebSocket connection to the
        remote host (IP address) identified by /host/, even if known by
        another name, wait until that connection has been established or
        for that connection to have failed.
However, when the WS is under proxies, we can't leak the host names to the DNS server. In this case, what should be done? I think the spec should clarify this.

Wellington.

v2.23.0 | Report a Bug | By Email