[Openid-specs-ab] Issue #2055: Charset of application/x-www-form-urlencoded requests/responses (openid/connect)

[Nat Sakimura]

It seems like a good idea though I am not sure if it can be permitted as an
errata.

On Thu, 31 Aug 2023 at 14:07, josephheenan via Openid-specs-ab <
openid-specs-ab at lists.openid.net> wrote:

> New issue 2055: Charset of application/x-www-form-urlencoded
> requests/responses
>
> https://bitbucket.org/openid/connect/issues/2055/charset-of-application-x-www-form
>
> Joseph Heenan:
>
> VP defines various http messages that have the content-type
> application/x-www-form-urlencoded.
>
> I cannot see anything that specifies the charset. Normally I think this
> would not matter too much as the content is normally ASCII - however I
> think presentation\_definition and presentation\_submission can contain
> non-ASCII characters \(couldn’t spot anything in [
> https://identity.foundation/presentation-exchange/](https://identity.foundation/presentation-exchange/#presentation-submission)
> that says anything either way\) so we should explicitly state UTF-8 charset
> to be used I think.
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20230831/193c4941/attachment.html>