Phil Jones

I'm not sure Hypercorn should always extract the TLS information - is this a costly operation?

Makes sense, I'd be happy with the ssl bool and the tls dictionary if the latter is enabled.

Fixed in 24aacf432ef44ddf8ba32e2427b507e560f63ce2

I don't think browsers try HTTP/3 by default, you'll need to serve over HTTP/1 or HTTP/2 and send an alt-serve header. [Here](https://github.com/pgjones/pgjones_dev/blob/c13aefe658d9f784cdbfa7244b45867a02122077/hypercorn.toml#L2) is an example.

Thanks for this, I've adapted it a bit and merged in d8de5f28adc99b1bc9b47a6c557fe25972ab966f

Thanks both, hopefully fixed with d16b50398aaedc509f83fe2b5c6c83a0ffbfc991

@kludex I think Starlette is doing the wrong thing here as per https://github.com/django/asgiref/issues/343, what do you think?

Should be fixed now given enough time has passed for release updates.

This is likely a bug with the `ProxyFixMiddleware` that is fixed in 0.17.0, just released.

Have you tried increasing the `wsgi_max_body_size` config variable?