Re: [websec] Strict-Transport-Security syntax redux

Julian Reschke <julian.reschke@gmx.de> Mon, 09 January 2012 00:39 UTC

Message-ID: <4F0A372B.2070407@gmx.de>
Date: Mon, 09 Jan 2012 01:39:07 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Adam Barth <ietf@adambarth.com>
References: <CAJE5ia-E1nhN1YGV6uy3uEq4oboQowDm4FboKbWV1kunHQmXPw@mail.gmail.com> <4EFCDDD5.6040005@gmx.de> <CAJE5ia8CL9ozRJgRNCdu6XwVT0paVuVUreB12f-BiMvH+wiq6A@mail.gmail.com> <4EFD73E6.1060506@gmx.de> <CAJE5ia8RBa8iCd_9TjXyzG54VASa6qqGomsO9gL-qQ2ia=BKLg@mail.gmail.com> <4EFD7C09.9050702@gmx.de> <CAJE5ia8aN_MKUX_7ehp6siw=CY7nC4aSRPoPcsaDX8+emwaFVw@mail.gmail.com> <4EFD8BCE.7010909@gmx.de> <CAJE5ia9cziSx-xb6nCEFXJkbu2Ls_ZQmYHpfrC7UK3ig3ZmM2g@mail.gmail.com> <4F052D2E.5050200@gondrom.org> <aoakg7l45gfcrj731u6k652hjofhv12ocl@hive.bjoern.hoehrmann.de> <CAJE5ia-5X_onfhUriRkQZNbVBa_qRBYPkUu8kyEVsrGmE41_=Q@mail.gmail.com>
In-Reply-To: <CAJE5ia-5X_onfhUriRkQZNbVBa_qRBYPkUu8kyEVsrGmE41_=Q@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, websec@ietf.org
Subject: Re: [websec] Strict-Transport-Security syntax redux
Precedence: list

On 2012-01-09 01:25, Adam Barth wrote:
> On Sun, Jan 8, 2012 at 4:10 PM, Bjoern Hoehrmann<derhoermi@gmx.net>  wrote:
>> * Tobias Gondrom wrote:
>>> <hat="chair>
>>> as it seems there is disagreement on how to resolve this, with only very
>>> few people having spoken out so far, I would like to invite comments
>> >from other working group members on this topic to see whether we might
>>> have missed something.
>>
>> It seems to me that all headers defined in RFC 2616 that allow para-
>> meteter lists of the `;name=value` form allow the value to be a quoted
>> string.
>
> This header isn't defined in RFC 2616 and many headers defined outside
> of RFC 2616 don't use quoted-string.
> ...

In name/value pairs? Example?

(As a matter of fact, not all header fields in 2616 are as consistent as 
they should, but that's not an excuse for not trying to do better with 
new header fields)

Best regards, Julian

[websec] Strict-Transport-Security syntax redux Ryan Sleevi
Re: [websec] Strict-Transport-Security syntax red… =JeffH
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
[websec] Strict-Transport-Security syntax redux =JeffH
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… =JeffH
Re: [websec] Strict-Transport-Security syntax red… =JeffH
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Phillip Hallam-Baker
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Bjoern Hoehrmann
Re: [websec] Strict-Transport-Security syntax red… Phillip Hallam-Baker
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… =JeffH
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Roy T. Fielding
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Tobias Gondrom
Re: [websec] Strict-Transport-Security syntax red… Anne van Kesteren
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Paul Hoffman
Re: [websec] Strict-Transport-Security syntax red… Anne van Kesteren
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Anne van Kesteren
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Bjoern Hoehrmann
Re: [websec] Strict-Transport-Security syntax red… Adam Barth
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Paul Hoffman
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Marsh Ray
Re: [websec] Strict-Transport-Security syntax red… Julian Reschke
Re: [websec] Strict-Transport-Security syntax red… Bjoern Hoehrmann