Issue:
The socket manager processes the entire request in handleClientData even if it exceeds the set max_body byte size. This is a massive waste of time and bandwidth. Simply stopping when the limit is reached and sending an early response will not work however, as it won't cleanly close the client connection.
Potential Solution:
When a request is received, parse the header completely independently from the body of the request and extract the body size metadata. Then, do not even start processing the body if it exceeds the max_body set for that location/server. This of course implies having to already know the relevant location this early into the runtime loop, which will require major restructuring of the request parsing system order.
Issue:
The socket manager processes the entire request in
handleClientDataeven if it exceeds the setmax_bodybyte size. This is a massive waste of time and bandwidth. Simply stopping when the limit is reached and sending an early response will not work however, as it won't cleanly close the client connection.Potential Solution:
When a request is received, parse the header completely independently from the body of the request and extract the body size metadata. Then, do not even start processing the body if it exceeds the
max_bodyset for that location/server. This of course implies having to already know the relevant location this early into the runtime loop, which will require major restructuring of the request parsing system order.