[OpenID] Content-Type for Key-Value Form response from OP

[Andrew Arnott]

Unless I hear any objection then, I'm going to code up my library to respond
with application/x-openid-kvf as the content-type for Key-Value Form encoded
messages.

Thanks for the help coming up with this, Martin.

Andrew Arnott

On Wed, Jun 11, 2008 at 4:59 PM, Andrew Arnott <andrewarnott at gmail.com>
wrote:

> (Forwarding to entire list since I hit Reply instead of Reply All).
>
>
> Thanks, Martin.  It sounds like application/x-kvf is better than text/kvf
> then.  Perhaps we can also be more descriptive then as say
> "application/x-openid-kvf"?
>
> Andrew Arnott
>
> On Wed, Jun 11, 2008 at 1:48 PM, Martin Atkins <mart at degeneration.co.uk>
> wrote:
>
>> Andrew Arnott wrote:
>> > In that case, I move that we adopt text/kvf as the official Content-Type
>> > for Key-Value Form encoding response messages.
>> >
>>
>> Hi Andrew,
>>
>> Sorry I didn't see your messages until now.
>>
>> I believe the convention for unregistered MIME types is to prefix the
>> subtype part with "x-", giving something like text/x-kvf.
>>
>> However, since the spec mandates UTF-8 for this message format, it may
>> be more appropriate to use an "application/" type; text types generally
>> support a "charset" attribute allowing the content to be in an arbitrary
>> character encoding, which is not appropriate here.
>>
>> _______________________________________________
>> general mailing list
>> general at openid.net
>> http://openid.net/mailman/listinfo/general
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20080613/e0f326dc/attachment-0001.htm>