Skip to content

Allow non-ASCII characters in response header values #4727

New issue
New issue
Closed
#33776
Closed
Allow non-ASCII characters in response header values#4727
#33776
Assignees
Tratcher
Labels
affected-fewThis issue impacts only small number of customersapi-suggestionEarly API idea and discussion, it is NOT ready for implementationarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-kestrelhelp wantedUp for grabs. We would accept a PR to help resolve this issueseverity-majorThis label is used by an internal tool
Milestone
6.0-preview7
@JunTaoLuo

Description

@JunTaoLuo
JunTaoLuo
opened on Sep 5, 2018

Following up for aspnet/KestrelHttpServer#1144. We may want to allow UTF-8 characters in response header values now to parallel our acceptance of UTF-8 characters in request header values. Note that the app has some degree of control over the response headers and their values.

Metadata

Metadata

Assignees

Labels

affected-fewThis issue impacts only small number of customersapi-suggestionEarly API idea and discussion, it is NOT ready for implementationarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-kestrelhelp wantedUp for grabs. We would accept a PR to help resolve this issueseverity-majorThis label is used by an internal tool

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions