IETF Logo Mail Archive

Re: [OAUTH-WG] Proposal for text for section 2

Eran Hammer-Lahav <eran@hueniverse.com> Wed, 30 June 2010 00:14 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 041FC3A69C0 for <oauth@core3.amsl.com>; Tue, 29 Jun 2010 17:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.235
X-Spam-Level:
X-Spam-Status: No, score=-2.235 tagged_above=-999 required=5 tests=[AWL=0.364, BAYES_00=-2.599]
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 dZF+CG5OW9nY for <oauth@core3.amsl.com>; Tue, 29 Jun 2010 17:14:19 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id EBEAD3A68AC for <oauth@ietf.org>; Tue, 29 Jun 2010 17:14:17 -0700 (PDT)
Received: (qmail 27431 invoked from network); 30 Jun 2010 00:14:27 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 30 Jun 2010 00:14:26 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Tue, 29 Jun 2010 17:14:25 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 29 Jun 2010 17:14:30 -0700
Thread-Topic: [OAUTH-WG] Proposal for text for section 2
Thread-Index: AcsXrGDU+cOkXD6yQpS4lCbUJEfEswANljAAAAGUYGA=
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3ED4BF7C@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <7C01E631FF4B654FA1E783F1C0265F8C579CC0C3@TK5EX14MBXC117.redmond.corp.microsoft.com> <7C01E631FF4B654FA1E783F1C0265F8C579D0F31@TK5EX14MBXC117.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E11265A5FC9D@WSMSG3153V.srv.dir.telstra.com> <AANLkTilrSUMEjsF-3RHuit6aoAPRe0DAqR6Uz2ldrd_l@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E11265B7E474@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E11265B7E474@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Proposal for text for section 2
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2010 00:14:27 -0000

More precisely, what are the actual deployed limits on HTTP *request* headers in popular HTTP servers like Apache and IIS, and in popular client platform likely to use this size assertions?

EHL

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Manger, James H
> Sent: Tuesday, June 29, 2010 5:08 PM
> To: Marius Scurtescu
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] Proposal for text for section 2
> 
> Marius,
> 
> >> For instance, why not define a SAML HTTP authentication mechanism:
> >>
> >>    Authorization: SAML a=<base64url-encoded SAML assertion>
> 
> > This came up in another thread, but SAML assertions could be too large
> > to be passed through an HTTP header. Other than that, your suggestion
> > really simplifies things.
> 
> What are the limits on HTTP headers?
> I don't think there are any in the HTTP spec.
> <http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-09#section-3.2>
> A comment in the other thread said SPNEGO headers can be up to 12392
> bytes and do not seem to be a problem.
> <http://www.ietf.org/mail-archive/web/oauth/current/msg03359.html>
> 
> I is hard to support a POST-and-form-only method when there is an
> alternative that "really simplifies things" without more concrete information
> on what the actual HTTP limits are (& how hard it is to increase them), and
> what practical assertion sizes are.
> 
> 
> --
> James Manger
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.46.0 | Report a Bug | By Email | System Status