<div dir="ltr">It seems like a good idea though I am not sure if it can be permitted as an errata. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 31 Aug 2023 at 14:07, josephheenan via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">New issue 2055: Charset of application/x-www-form-urlencoded requests/responses<br>
<a href="https://bitbucket.org/openid/connect/issues/2055/charset-of-application-x-www-form" rel="noreferrer" target="_blank">https://bitbucket.org/openid/connect/issues/2055/charset-of-application-x-www-form</a><br>
<br>
Joseph Heenan:<br>
<br>
VP defines various http messages that have the content-type application/x-www-form-urlencoded.<br>
<br>
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 [<a href="https://identity.foundation/presentation-exchange/%5D(https://identity.foundation/presentation-exchange/#presentation-submission)" rel="noreferrer" target="_blank">https://identity.foundation/presentation-exchange/](https://identity.foundation/presentation-exchange/#presentation-submission)</a> that says anything either way\) so we should explicitly state UTF-8 charset to be used I think.<br>
<br>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div>