Skip to content
This repository was archived by the owner on Mar 19, 2019. It is now read-only.

Handle null and empty valued response headers #158

Closed
JunTaoLuo opened this issue Dec 9, 2015 · 1 comment
Closed

Handle null and empty valued response headers #158

JunTaoLuo opened this issue Dec 9, 2015 · 1 comment
Assignees

Comments

@JunTaoLuo
Copy link
Contributor

Similar to aspnet/KestrelHttpServer#429, setting null values in a multi-valued known header will crash the server.

The expected behaviour is null values for headers should be ignored both for known and unknown headers. Header values of empty strings will be ignored for known headers due to API limitations but will be sent in the response for unknown headers.

@JunTaoLuo
Copy link
Contributor Author

To reduce unnecessary filtering, it was decided to convert all null headers to empty headers and let Http.Sys decide whether it's included in the response. Currently, Http.Sys will ignore null/empty known headers but will keep null/empty unknown headers.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant