Closed rrrnld closed 5 years ago
Actually this seems to be more complicated than I thought first. It does not apply to special characters in general but non ascii chars like (äöü etc.) but device-id and push url should not contain non ascii chars. Therefore we do not need a fix to this.
Hm, you're right that maybe we don't need to fix this, but responding with a more appropriate status code like 422
or 400
would still be nice (this way we could be sure that with response 500
we messed up unintentionally).
Unfortunately Kestrel can't handle utf-8 request headers right now, so we can not handle them on our own.
To reproduce:
Interestingly this happens mainly with Umlauts in the
X-Push-URL
orX-Device-ID
header.