Skip to content

Implement HPack dynamic compression #4715

Closed
@Tratcher

Description

@Tratcher

Today Kestrel does not use any of the HPack compression features when serializing response headers. Dynamic compression is an advanced option we could look into.

Likely candidates:

  • Server: Kestrel
  • Content-Encoding: gzip
  • Content-Encoding: brotli
  • Content-Type (and a dozen common values)
  • strict-transport-security

Note the client gets more benefits from dynamic compression, especially browsers, they send a lot of repetitive headers. HttpClient would get some benefit for things like :authority, :method, :scheme, accept-encoding,

Related work:

Metadata

Metadata

Assignees

Labels

HTTP2Perfarea-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-kestrel

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions