cowboy.git/src, branch 2.8.0 Small, fast, modern HTTP server for Erlang/OTP. 204 and 304 responses must not include a body 2020-05-20T11:41:05+00:00 Loïc Hoguin essen@ninenines.eu 2020-05-20T11:41:05+00:00 39b2816255503910dc23e2fdf703ee63bbc8953e When calling cowboy_req:reply/4 with a body a crash will occur resulting in a 500 response. When calling cowboy_req:stream_reply/2,3 and then attempting to send a body a crash will occur. 
When calling cowboy_req:reply/4 with a body a crash will occur
resulting in a 500 response. When calling cowboy_req:stream_reply/2,3
and then attempting to send a body a crash will occur.
Increase the default max_keepalive HTTP option to 1000 2020-05-20T09:08:58+00:00 Loïc Hoguin essen@ninenines.eu 2020-05-20T09:08:58+00:00 8337aca4d31ffa8120704057675aacbbaa280975 100 is very low for current deployments. 1000 is more appropriate as a default value. 
100 is very low for current deployments. 1000 is more
appropriate as a default value.
Experiment with a linger_timeout for HTTP/2 2020-04-06T12:50:35+00:00 Loïc Hoguin essen@ninenines.eu 2020-04-06T12:50:35+00:00 775091134dc49633595cfc5956612df0c5702c0f This is mostly to ensure that the GOAWAY frame is properly received on Windows in some tests, but should be benefitial also in production in particular when clients are slower. 
This is mostly to ensure that the GOAWAY frame is properly
received on Windows in some tests, but should be benefitial
also in production in particular when clients are slower.
Fix active mode and flow control during pipelining 2020-04-04T18:15:23+00:00 Loïc Hoguin essen@ninenines.eu 2020-04-04T18:15:23+00:00 4ab69f402e38f77b7612ecf30f3defe9c6a76d24 We could get stuck in passive mode under certain conditions (fast and non-busy machine and perhaps other environment factors). 
We could get stuck in passive mode under certain conditions
(fast and non-busy machine and perhaps other environment factors).
Fix h2spec "invalid preface sequence" test 2020-04-01T16:02:59+00:00 Loïc Hoguin essen@ninenines.eu 2020-04-01T16:02:59+00:00 a8a26897274c798cb95d3a2e9e8da1215c2da78a Introduce a currently undocumented option to allow disabling cowboy_http when using a clear listener. 
Introduce a currently undocumented option to allow disabling
cowboy_http when using a clear listener.
Add more headers to cowboy_req:parse_header/2,3 2020-03-30T13:02:35+00:00 Loïc Hoguin essen@ninenines.eu 2020-03-30T12:54:48+00:00 0fc33c53001e577f52377c520ec8199b9a0682f2 






Add more router tests
2020-03-29T13:44:47+00:00

Loïc Hoguin
essen@ninenines.eu

2020-03-29T13:44:47+00:00

70e43ec11213e2e8f43f0ec4e407ea3dc7120fe1












Increase the default max_received_frame_rate
2020-03-29T11:51:21+00:00

Loïc Hoguin
essen@ninenines.eu

2020-03-29T11:51:21+00:00

6ad842a742915066d319f307a0f60cd8df15598b

Allow 10000 frames every 10 seconds instead of just 1000,
as the limit was too quickly reached in some deployments.





Allow 10000 frames every 10 seconds instead of just 1000,
as the limit was too quickly reached in some deployments.







Fix HTTP/1.1 bug when a flow command is returned after fin
2020-02-07T10:32:15+00:00

Loïc Hoguin
essen@ninenines.eu

2020-02-07T10:32:15+00:00

8fc3da2fc31a04281b0ba8dc0cdc1e1650067da5

This resulted in a badarith error due to the current flow being
set to infinity when the body has been fully read. A test case
has been added reproducing the issue.





This resulted in a badarith error due to the current flow being
set to infinity when the body has been fully read. A test case
has been added reproducing the issue.







Fix bugs related to HTTP/1.1 pipelining
2020-01-17T10:42:28+00:00

Loïc Hoguin
essen@ninenines.eu

2020-01-16T16:33:49+00:00

752297b1539b4f74c9329c873f78485a52b5b8bd

The flow control is now only set to infinity when we are
skipping the request body of the stream that is being
terminated. This fixes a bug where it was set to infinity
while reading a subsequent request's body, leading to a
crash.

The timeout is no longer reset on stream termination.
Timeout handling is already done when receiving data
from the socket and doing a reset on stream termination
was leading to the wrong timeout being set or the right
timeout being reset needlessly.





The flow control is now only set to infinity when we are
skipping the request body of the stream that is being
terminated. This fixes a bug where it was set to infinity
while reading a subsequent request's body, leading to a
crash.

The timeout is no longer reset on stream termination.
Timeout handling is already done when receiving data
from the socket and doing a reset on stream termination
was leading to the wrong timeout being set or the right
timeout being reset needlessly.