We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For each request from the browser a lot of repeated headers are sent that are identical to the previous request.
This results in a lot of string allocations, especially for Accept, Cookie and User-Agent e.g.
Accept
Cookie
User-Agent
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8 Accept-Encoding: gzip, deflate, br Accept-Language: en-US,en;q=0.9 Cache-Control: no-cache Connection: keep-alive Cookie: (**redacted up to 2KB of data**) Host: github.com Pragma: no-cache Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36
The previous request has already materialized these values as strings, so they could be reused rather than allocating new strings.
Tracking issue
In March 5th, 2019's ASP.NET Community Standup, @DamianEdwards expressed that he thought this was already happening; then continued to suggest that in a future version it would be important to continue to reduce memory used for headers.
/cc @davidfowl
The text was updated successfully, but these errors were encountered:
Hi, how does it relate to http2 header compression ?
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
For each request from the browser a lot of repeated headers are sent that are identical to the previous request.
This results in a lot of string allocations, especially for
Accept
,Cookie
andUser-Agent
e.g.Describe the solution you'd like
The previous request has already materialized these values as strings, so they could be reused rather than allocating new strings.
Additional context
Tracking issue
In March 5th, 2019's ASP.NET Community Standup, @DamianEdwards expressed that he thought this was already happening; then continued to suggest that in a future version it would be important to continue to reduce memory used for headers.
/cc @davidfowl
The text was updated successfully, but these errors were encountered: