[ogpx] identifying a malformed LLSD request with HTTP binding
Meadhbh Hamrick <ohmeadhbh@gmail.com> Mon, 29 March 2010 16:04 UTC
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A286A3A6AA0 for <ogpx@core3.amsl.com>; Mon, 29 Mar 2010 09:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.038
X-Spam-Level: *
X-Spam-Status: No, score=1.038 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 gy3oqL+X0GJw for <ogpx@core3.amsl.com>; Mon, 29 Mar 2010 09:04:52 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by core3.amsl.com (Postfix) with ESMTP id C68263A68EF for <ogpx@ietf.org>; Mon, 29 Mar 2010 09:03:36 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 9so296684qwb.31 for <ogpx@ietf.org>; Mon, 29 Mar 2010 09:04:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:received :message-id:subject:to:content-type; bh=Sk/mO6f/2eZzj4tizBgH1Z+VpuJwLwQuihqpwFgnoFg=; b=VRP0JxW8OFpXpx/kXs33VDiFKryY06ErZJeQ63YlMmbtac7h3VPgUU7n/pqSrxCVm6 zMPGsP9b48v8GEnEznHfHTAc8negecBoOkAdn3NELFeK6ZF1wjhE3qP4FZVXNN49JI0e X2kXRBrE5os5CHILTdENpeIVgoat9Xv45c8c0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=D7Y/BI7Hv3y7zOwHVFG9U/rzLYdY7sOoIDo9jAL8RxeraZ4c7FkAx5VxG0cBZwup74 OG57oUKQCIPL/MuAaoJ79kYZOb3Fl7xADtMy4sAFyccWVSjIeYr0qclF59FCnbpu81Pb XWh0vEPxkm5bfxoufsW7IDQSf3MuZ9NDnecOQ=
MIME-Version: 1.0
Received: by 10.229.20.209 with HTTP; Mon, 29 Mar 2010 09:03:41 -0700 (PDT)
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Mon, 29 Mar 2010 09:03:41 -0700
Received: by 10.229.251.69 with SMTP id mr5mr1119392qcb.91.1269878641264; Mon, 29 Mar 2010 09:04:01 -0700 (PDT)
Message-ID: <b325928b1003290903l4e060d2bxd4f7f2dbdf1ba455@mail.gmail.com>
To: ogpx <ogpx@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [ogpx] identifying a malformed LLSD request with HTTP binding
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2010 16:04:53 -0000
so i think we said we wanted to make it easier to bind LLSD to different transports. but the one that was going to be defined "out of the box" as HTTP. so assuming there is consensus to reject malformed LLSD messages, allow me to ask, how do we signal the fact that a server receiving a HTTP request believes the message was malformed? reply with a 400 : Bad Request ? ultimately i think we'll have to identify these conditions in a transport neutral manner, and then map them to the transport, but for the sake of expediency for people who may want to write interoperable systems using HTTP, can we agree to this at the moment? -cheers -meadhbh -- meadhbh hamrick * it's pronounced "maeve" @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com
- [ogpx] identifying a malformed LLSD request with … Meadhbh Hamrick
- Re: [ogpx] identifying a malformed LLSD request w… Robert G. Jakabosky