Lighttpd

This is not a bug, since server.max-request-size is operating as advertised.

It appears that you are suggesting that request size limit should not apply to websocket requests. It is reasonable that you desire that behavior. Is it the right behavior for everyone?

The patch you have proposed is incorrect for other reasons, such as logging and accounting, not to mention that part of your patch deletes the comment
/*(not chunkqueue_reset(); do not reset cq->bytes_in, cq->bytes_out)*/
and calls chunkqueue_reset() Did you really think the comment you deleted had no meaning?

A simpler patch would have set the configuration to disable the limit for the wstunnel request. (r->conf.max_request_size = 0;)

However, the lighttpd default server.max-request-size = 0 does not enforce a limit.

If you have configured a limit in your lighttpd configuration, then you have the option of creating a condition in lighttpd.conf to apply the limit to the scripts to which it should apply, or you can set server.max-request-size = 0 in a condition that matches what is handled by websockets.

$HTTP["url"] =~ "^/ws/" {
    server.max-request-size = 0
    wstunnel.server = ("" => ... )
}

The current lighttpd behavior allows a user to configure server.max-request-size for wstunnel connections.
lighttpd configuration allows either behavior to be specified (limit or no limit), so why should lighttpd change?
Why is the behavior you are suggesting the correct behavior for everyone, and why is the current lighttpd behavior incorrect?