Description
Is your feature request related to a problem? Please describe.
I need "the ability to limit the size of Request Header".
Although it is possible to implement this in an application, I think it is most efficient if it can be handled at the protocol implementation level.
Describe the solution you'd like
Currently, it is supported to specify the number of headers through the "h1_max_headers" option when creating a builder. I think it would be okay to control it by adding a few properties like this.
Describe alternatives you've considered
If we implement the header max setting, there may be several ways to do this.
- number of header: already implemented
- max size of each heade name: Fixed at 64kb
- max size of each heade value: none (maybe)
- max size of total header: none
What if all of this could be set as a builder option? What do you think about this?
Question
If the problem was simple, I would implement it myself and post a PR, but a question arose while looking at the code.
There is evidence of an attempt to add an option called "h1_max_header_size". What exactly is the max that this is trying to implement?