Re: [hybi] Fwd: failed TLS handshake: which close code?

John Tamplin <jat@google.com> Mon, 24 October 2011 16:28 UTC

Return-Path: <jat@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 A984011E808C for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 09:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.885
X-Spam-Level:
X-Spam-Status: No, score=-105.885 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 nV8n-ezbQUTW for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 09:28:38 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id D24FB11E8083 for <hybi@ietf.org>; Mon, 24 Oct 2011 09:28:37 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id p9OGSW4C031684 for <hybi@ietf.org>; Mon, 24 Oct 2011 09:28:32 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1319473712; bh=DqRUcMM4MqwZFUGeufnKfG9xvTI=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=uZodc9LbL2c8S6rIRR48eLlmdY1kUvRlR9B/PTIqbNqc2UW7Seeqqgtx29LxkyQVo uyTk608I5sVj/NXv9sCeQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=vPmC3duaFSsl2QsuOccc4phlDiSXalpJjDO97EfXi82s1Itk1KrSfY0RIwyv8gRxq 2gsCxJilKZeDu3HpmkY6Q==
Received: from yxn16 (yxn16.prod.google.com [10.190.4.80]) by hpaq12.eem.corp.google.com with ESMTP id p9OGLmmc018517 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Mon, 24 Oct 2011 09:28:31 -0700
Received: by yxn16 with SMTP id 16so2856472yxn.4 for <hybi@ietf.org>; Mon, 24 Oct 2011 09:28:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=U2qKBIfuqh5pscjJVmKTjRcjQQc4qNKf8eQAic2hkFk=; b=pVmAUFQbSRMYq5OB1dwZ0sqBtHw5PRIcAzbTgNREVORXNtvMsJigunCIXl3xWcPUD0 iZCc9pE56hxH92Ca1++A==
Received: by 10.150.214.1 with SMTP id m1mr11728099ybg.89.1319473711605; Mon, 24 Oct 2011 09:28:31 -0700 (PDT)
Received: by 10.150.214.1 with SMTP id m1mr11728080ybg.89.1319473711464; Mon, 24 Oct 2011 09:28:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.96.7 with HTTP; Mon, 24 Oct 2011 09:28:11 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D42D0B036EF5@EXVMBX020-12.exch020.serverdata.net>
References: <634914A010D0B943A035D226786325D42D0B036D6D@EXVMBX020-12.exch020.serverdata.net> <CADkeqZXXRkXCRrONLr5thwOqNVUxNWU0Q-9E0R0i=4S-bc-LFw@mail.gmail.com> <CADkeqZXDvu-JY8aZHJJPRH-_JnF196JjA_JG6X_1yrYSiAekuA@mail.gmail.com> <0ED03DDD-1AF9-41F9-B5F0-2968BF16E378@zaphoyd.com> <CADkeqZVvU31ML8tDAeYwnndvPZ9W8vEuzJksBm-4d1qv7MWObw@mail.gmail.com> <634914A010D0B943A035D226786325D42D0B036E9D@EXVMBX020-12.exch020.serverdata.net> <D5E88D14-C13E-490D-933E-6B133BAF98E3@bbn.com> <634914A010D0B943A035D226786325D42D0B036EF5@EXVMBX020-12.exch020.serverdata.net>
From: John Tamplin <jat@google.com>
Date: Mon, 24 Oct 2011 12:28:11 -0400
Message-ID: <CABLsOLBq-BiCRV8J84Rs6gHzAuO+wzTYpkQ45d3HBb=LYVsCxA@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary="000e0cd355f0dcc20d04b00de9f1"
X-System-Of-Record: true
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] Fwd: failed TLS handshake: which close code?
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, 24 Oct 2011 16:28:38 -0000

On Mon, Oct 24, 2011 at 12:25 PM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> Anyway: what is your recommendation for WS API for _apps_ (JavaScript) to
> recognize "invalid server cert"?
>

As this doesn't have anything to do with the wire protocol, that question
would be better asked on the WHATWG list for the WS API.

-- 
John A. Tamplin
Software Engineer (GWT), Google