RFC 8187 - Character Encoding for Headers
benaadams opened this issue · 1 comments
benaadams commented
From aspnet/KestrelHttpServer#2063
Hot off the presses (September 2017) https://tools.ietf.org/html/rfc8187
Indicating Character Encoding and Language for HTTP Header Field Parameters
@Tratcher Hmm, interesting choices. It only applies to key value pairs within headers, and is ASCII compatible, so I don't foresee making any changes to Kestrel. Microsoft.Net.Http.Headers in HttpAbstractions looks like the most obvious consumer/producer of such values. ContentDispositionHeaderValue already supports this because it was designed for use in multipart MIME bodies:
Move to HttpAbstractions?
aspnet-hello commented
This issue was moved to dotnet/aspnetcore#2688