Loïc Hoguin
Loïc Hoguin
Should be done across all Cowboy, not just in cowboy_static. See https://github.com/ninenines/cowboy/pull/514 for an old reference.
We could for example crash (instead of asking for more) if a part is too large, if there are too many parts, etc. This would make code simpler for many...
Currently we only limit how much data is to be read, and how long, per read_body calls. We need at least to define how many read_body a read_part/read_part_body call can...
There's basically no reasons not to send it, it's small and cheap to build. Currently we send it on 405 and OPTIONS responses, but it's probably best to always send...
Maybe just a list of related files would be enough. Then if we statically serve some HTML, we can put the CSS/JS in the list and it will be pushed...
As shown in https://github.com/ninenines/gun/pull/290 it can loop infinitely if bad options are given.
Sometimes the client is sending much faster than the server is able to process, and the client gets stuck sending data. Then the server may also get stuck when sending...
https://www.ietf.org/rfcdiff?url2=draft-ietf-httpbis-rfc6265bis-07 There's now a `default` value that is equivalent to `lax`. The code should reflect this.
`gun:ws_upgrade(ConnPid, Path, Headers, #{protocols => [...]})` Followup to #281.
The branch `http2-connect` has been merged. Some points remain for improved support though. * [x] HTTP/2 timeouts are not propagated to the right layer. This will require Cowlib changes, hopefully...