[Kestrel] Support for custom decoder for parsing target (e.g. URL)
Open
affected-very-few
area-networking
enhancement
feature-kestrel
severity-minor
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 276
Description
Follow up to #17400. The idea is to make the encoding Kestrel interprets the target as configurable. Currently, Kestrel only accepts ASCII targets. This could be done with something like a "TargetEncoding" Encoding property on KestrelServerOptions.
Contributor guide
Assessment
This issue has not been assessed yet.