Re: [ogpx] identifying a malformed LLSD request with HTTP binding
"Robert G. Jakabosky" <bobby@sharedrealm.com> Mon, 29 March 2010 22:45 UTC
Return-Path: <bobby@sharedrealm.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 248E93A6851 for <ogpx@core3.amsl.com>; Mon, 29 Mar 2010 15:45:21 -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 nw4Q3EdJ12fa for <ogpx@core3.amsl.com>; Mon, 29 Mar 2010 15:45:20 -0700 (PDT)
Received: from mail.neoawareness.com (ns2.sharedrealm.com [IPv6:2001:470:1f05:4f4::13]) by core3.amsl.com (Postfix) with ESMTP id F171B3A681D for <ogpx@ietf.org>; Mon, 29 Mar 2010 15:45:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=[10.200.0.30]) by mail.neoawareness.com with esmtpa (Exim 4.69) (envelope-from <bobby@sharedrealm.com>) id 1NwNiL-0005ap-Jk for ogpx@ietf.org; Mon, 29 Mar 2010 15:45:45 -0700
From: "Robert G. Jakabosky" <bobby@sharedrealm.com>
To: ogpx@ietf.org
Date: Mon, 29 Mar 2010 14:45:41 -0800
User-Agent: KMail/1.9.10
References: <b325928b1003290903l4e060d2bxd4f7f2dbdf1ba455@mail.gmail.com>
In-Reply-To: <b325928b1003290903l4e060d2bxd4f7f2dbdf1ba455@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201003291545.41626.bobby@sharedrealm.com>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bobby@sharedrealm.com
X-SA-Exim-Scanned: No (on mail.neoawareness.com); SAEximRunCond expanded to false
Subject: Re: [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 22:45:21 -0000
On Monday 29, Meadhbh Hamrick wrote: > 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? The HTTP 400 response can have a response body. For websites the response body is normally a HTML page that the browser can display to the user. Maybe a LLSD error message can be defined for use as the response body. Other transports can use that same LLSD message layout. -- Robert G. Jakabosky
- [ogpx] identifying a malformed LLSD request with … Meadhbh Hamrick
- Re: [ogpx] identifying a malformed LLSD request w… Robert G. Jakabosky