IETF Logo Mail Archive

[hybi] RFC6455 clarification: when received close code of 1005, 1006, 1015

Takeshi Yoshino <tyoshino@google.com> Wed, 09 May 2012 05:12 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 DF76621F84DE for <hybi@ietfa.amsl.com>; Tue, 8 May 2012 22:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.939
X-Spam-Level:
X-Spam-Status: No, score=-102.939 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 ScBwKOzS6m-0 for <hybi@ietfa.amsl.com>; Tue, 8 May 2012 22:12:41 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 04E2021F84D6 for <hybi@ietf.org>; Tue, 8 May 2012 22:12:40 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so2336912ggm.31 for <hybi@ietf.org>; Tue, 08 May 2012 22:12:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record; bh=nTEDi3lMF+PzhMub7X2X4Fi45ras8NF7hcomFLY0xm0=; b=DHxYQTAjUHT5skM0lOjUa68vRisSaB69HmPMHVJPSmNNXIRtbvbnqt6+odDMAjG79U ACU96lSL/1T7h4tfIxXEIl/c6/AJIYgJ50wVPp3+BqbpkKR4wXt4vg5RB2pcEyhaw1sh mqB2Or70mO125xaaGeOmomNl0srxl9QZscIomVks7tXWalQ1SQGrM5xgC2YLB4gIQAFK Po44Y/PMp+dwAjNL9aI6oXXxSTSRzsYT+p3BmW3EyxgVBGA2Ac3sHY9p0ZzjZKpkdNWd jj7zGbcC627ZQJ1aNg/9kTh/ZyWXz+5/f/Lpk/S2zz4A/mMNsZuIK7hWwgm9JHMYzsaH oeVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record:x-gm-message-state; bh=nTEDi3lMF+PzhMub7X2X4Fi45ras8NF7hcomFLY0xm0=; b=DqapqjwnHyBc5VOfJryxsUfsFWNuB2IOtuwyFsDA+d9TbdWBrTUdglGtvN+xI2fM6l QzFhbZM5j7Gqz0DRtRgzSi3A0/fFtALZpnvLrkdJrttkMuhYa65lLetX3pM6ZbNiCGo7 1ie72Eqam0NMBCvpJY9P7bYiPHiJxYIXymiWZtKIutz+ZqwWOJRrJ/h8BvxX/QgrhjBB JkmMA5vKOzqfJQp8jUYKKQyIIAqS2WM4ScoQLe54PLbsJgMfpBRpCHfNm0UmJY9TPXup b9R1oyL5Pj6JDfCKJ46qvXDh6ddjWFK+nU6oFie35tX2Kf3wpSlYWAfQwSNz0c8t08og P3OQ==
Received: by 10.50.222.137 with SMTP id qm9mr1971280igc.64.1336540360425; Tue, 08 May 2012 22:12:40 -0700 (PDT)
Received: by 10.50.222.137 with SMTP id qm9mr1971275igc.64.1336540360349; Tue, 08 May 2012 22:12:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.112.130 with HTTP; Tue, 8 May 2012 22:12:19 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 09 May 2012 14:12:19 +0900
Message-ID: <CAH9hSJbQ7dcu4N=Yf7TyFzJ0FhfVRehEMtnFx3Qvv_W0T5Cs+A@mail.gmail.com>
To: hybi@ietf.org
Content-Type: multipart/alternative; boundary="14dae93410736817c704bf938d89"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkSdNHf6ZpGWmyBnqbf1septFbboKT1edaAc+ahFAqaZ+mEaO/4LadVNCHVbv8pLWQr0d+/Z+ZEn5oTf1X66RDLcrhr0gbY0I8QVI1QjCIQKImqL6/AjLgUfp+vz4OKM4FGugdu
Subject: [hybi] RFC6455 clarification: when received close code of 1005, 1006, 1015
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: Wed, 09 May 2012 05:12:42 -0000

Hi,

Endpoints MUST NOT send a close frame with close code of 1005, 1006 or 1015.

What should we do when received such a frame from a broken endpoint? It
seems there's no text specifying this.

I think this should be taken as protocol error. The endpoint received such
a bad close frame should _Fail the WebSocket Connection_ and invoke
onclose() with code=1006 and wasClean=false.

Thoughts?

Takeshi

v2.23.0 | Report a Bug | By Email