Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

badmatch, {error,closed} when closing the connection with loop handler #806

Closed
semir-karic opened this issue Mar 25, 2015 · 2 comments
Closed
Labels

Comments

@semir-karic
Copy link

After the loop has started, if connection gets closed (eg:close the browser while waiting for response) I get the following error report:

=ERROR REPORT==== 25-Mar-2015::11:26:18 ===
Error in process <0.167.0> with exit value: {{badmatch,{error,closed}},[{cowboy_req,response,6,[{file,"src/cowboy_req.erl"},{line,1049}]},{cowboy_req,reply_no_compress,8,[{file,"src/cowboy_req.erl"},{line,796}]},{cowboy_req,reply,4,[{file,"src/cowboy_req.erl"},{line,751}]},{cowboy_req... 


=ERROR REPORT==== 25-Mar-2015::11:26:18 ===
Ranch listener my_http_listener had connection process started with cowboy_protocol:start_link/4 at <0.167.0> exit with reason: {{badmatch,{error,closed}},[{cowboy_req,response,6,[{file,"src/cowboy_req.erl"},{line,1049}]},{cowboy_req,reply_no_compress,8,[{file,"src/cowboy_req.erl"},{line,796}]},{cowboy_req,reply,4,[{file,"src/cowboy_req.erl"},{line,751}]},{cowboy_req,ensure_response,2,[{file,"src/cowboy_req.erl"},{line,883}]},{cowboy_protocol,next_request,3,[{file,"src/cowboy_protocol.erl"},{line,488}]}]}
@essen
Copy link
Member

essen commented Jul 13, 2015

This one is "normal", ie the crash happened when trying to send data. However I agree the error message is a bit annoying.

@essen essen added the Bug label Aug 15, 2015
@essen essen modified the milestone: 2.0.0 Aug 18, 2015
@essen essen modified the milestones: 2.0.0, 2.0 Tasks Feb 3, 2017
@essen essen removed this from the 2.0 Tasks milestone Oct 2, 2017
@essen
Copy link
Member

essen commented Dec 12, 2017

Shouldn't be a problem in 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants