cowboy
cowboy copied to clipboard
ninenines
Small, fast, modern HTTP server for Erlang/OTP.
if the url param has a base64 image , it's end with "=", then cow_qs:parse_qs can't handler it right
I'm having an error similar to https://github.com/ninenines/cowboy/issues/1411 but instead of `flow = infinity`, I've got `Size = infinity`. I'm using cowboy 2.9.0 and Elixir 1.12-otp24. It only happens from time...
bug: Missing echo parameter crasher: initial call: cowboy_stream_h:request_process/3 echo(undefined, Req) -> cowboy_req:reply(400, [], , Req); echo(Echo, Req) -> cowboy_req:reply(200, #{ => }, Echo, Req). ==》》 echo(undefined, Req) -> cowboy_req:reply(400, #{},...
First I tried to set max_age to 0, as recommended in cowboy documentation: Req1 = cowboy_req:set_resp_cookie(utils:to_binary(SessionCookieName), , Req0, #{max_age => 0}), The cookie was not deleted by browser. Then I...
Relates to #1511 Adds handler to capture external exits of processes, and tests to verify this is indeed happening. On my Elixir/Phoenix project, where I add such line in a...
When a web request is being processes by Cowboy, and the request handling process get sent exit signal (as in with `exit/2`), it seems like the process is silently crashing...
Currently, if HTTP/1.1 is used with a cowboy connection that has been configured with `connection_type == worker`, the first request will succeed with the connection and a second request performed...
With cowboy1 source code using `{ping,}` worked. However, with the current master branch source code `{ping,}` may be provided though the connection doesn't get a `{pong, _}` in the future....
Encountering the following crash post upgrade from 2.7.0 to 2.8.0 and had to revert the upgrade: `2021-03-08 10:31:35.812 [error] @cowboy_req:reply:812 CRASH REPORT Process with 0 neighbours crashed with reason: no...
`cowboy_req:match_qs` for constraints given as {Key, Constraint} crashes with `badkey` error if key is missing. Expected behaviour is to crash with `required` error.
