cowboy.git/src, branch corral

WIP, not going to compile

2026-04-02T13:17:54+00:00

WIP

2026-03-31T13:16:42+00:00

HTTP/1: Allow independent max authorization/cookie length

2025-10-14T10:02:51+00:00

Adds two options:

 * max_authorization_header_value_length to configure the
   maximum length of the authorization header specifically;

 * max_cookie_header_value_length to configure the
   maximum length of the cookie header specifically.

LH: I added the relevant tests.

Fully disable quicer/h3 unless COWBOY_QUICER is set

2025-10-07T16:19:40+00:00

This should avoid Dialyzer errors.

A CI job testing without COWBOY_QUICER has also been added.

Make HTTP/2 Websocket call terminate/3 on socket close

2025-09-30T09:28:07+00:00

The close reason will differ from HTTP/1.1 because we don't
have access to the socket. Also trapping exits is required
to process the 'EXIT' signal and call terminate/3.

cowboy_rest: Allow last_modified to return undefined

2025-09-17T13:10:16+00:00

Use raw mode to read from the file info

2025-09-17T13:02:24+00:00

Rescue from https://github.com/ninenines/cowboy/pull/1687

See https://erlangforums.com/t/cowboy-2-13-0-performance-bottleneck-at-8-7k-rps-on-erlang-28-0-2/5004

Co-authored-by: Zabrane

Make dynamic_buffer start at 512 and change less abruptly

2025-09-16T12:05:39+00:00

Based on RabbitMQ performance testing. In RabbitMQ we start
at 128 instead but 128 is too low for typical HTTP requests.

New data delivery mechanism for HTTP/2+ Websocket

2025-09-15T11:09:23+00:00

A new data_delivery mechanism called 'relay' has been added.
It bypasses stream handlers (and the buffering in cowboy_stream_h)
and sends the data directly to the process implementing
Websocket (and should work for other similar protocols
like HTTP/2 WebTransport).

Flow control in HTTP/2 is maintained in a simpler way,
via a configured flow value that is used to maintain
the window to a reasonable value when data is received.

The 'relay' data_delivery has been implemented for both
HTTP/2 and HTTP/3. It has not been implemented for HTTP/1.1
since switching protocol there overrides the connection process.

HTTP/2 Websocket is now better tested.

A bug was fixed with the 'stream_handlers' data_delivery
where active mode would not be reenabled if it was disabled
at some point.

The Websocket performance suite has been updated to
include tests that do not use Gun. Websocket modules
used by the performance suite use the 'relay' data_delivery
now. Performance is improved significantly with 'relay',
between 10% and 20% faster. HTTP/2 Websocket performance
is not on par with HTTP/1.1 still, but the remaining
difference is thought to be from the HTTP/2 overhead and
flow control.

Update to most recent WebTransport draft

2025-06-25T09:47:25+00:00

WEBTRANSPORT -> WT in most places. Only ENABLE_WEBTRANSPORT
remains (since it is a draft-02 setting that was later removed)
as well as internal functions and atoms about stream headers,
for greater clarity.

The draft also clarified that WT_SESSION_GONE can be sent on
the session stream and since it's what is already done a
related todo was removed.