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

[Andrew Arnott]

I guess no one knows what the best thing to do is here?

On Tue, May 27, 2008 at 7:11 AM, Andrew Arnott <andrewarnott at gmail.com>
wrote:

> I'm looking for a suggested Content-Type to use when sending OP direct
> messages (Key-Value Form).  The default web servers are sending (at least
> mine) is text/html.  But not only is text/html inaccurate (as is text/plain,
> to a lesser degree), but some free hosts (like GoDaddy's free hosting) will
> tack on an advertising <script> tag at the end of any message leaving the
> server if it is text/html or text/plain, which invalidates the Key-Value
> Encoding.
>
> I have tested application/openidkvf and that allows an OP to be hosted on
> GoDaddy free hosting sites without having its direct message responses
> corrupted by the <script> tag.  But I see a few issues with this
> content-type:
>
>    1. Some firewalls may block it as an unknown content-type (I've already
>    heard reports of firewalls blocking application/xrds+xml).
>    2. It doesn't look that nice.
>    3. Other OpenID Providers may be using something different, and it
>    would be nice to standardize.
>
> Is there any content-type that others are using for this, or that you might
> recommend?
>
> Thanks.
>
> --
> Andrew Arnott




-- 
Alanis Morissette  - "We'll love you just the way you are if you're
perfect."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20080607/c0af5b30/attachment-0002.htm>