# Canceled/abandoned request to Mongrel/Ruby

**URL:** <https://www.ruby-forum.com/t/canceled-abandoned-request-to-mongrel-ruby/162098>\
**Category:** Rails\
**Created:** [March 5, 2009, 6:19pm UTC](https://www.ruby-forum.com/t/canceled-abandoned-request-to-mongrel-ruby/162098 "2009-03-05T18:19:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael\_teter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/e47c2d/32.png) [@michael\_teter](https://www.ruby-forum.com/u/michael_teter)\
**Post date:** [March 5, 2009, 6:19pm UTC](https://www.ruby-forum.com/t/canceled-abandoned-request-to-mongrel-ruby/162098/1 "2009-03-05T18:19:39Z")

</div>

Howdy.

I’m wondering what happens in Mongrel/Ruby when a user asks for a page  
but then hits Stop in the browser or just clicks a different link  
before the response comes back.

The reason I ask is that the app I’m building does a fair amount of  
database work on each page. From what I can tell, when a user  
abandons a request, the server has no awareness of this and thus  
continues waiting for the database to serve it so it can respond to  
the user.

Is there some mechanism or best practice to stop this? With the  
single-threaded nature of Ruby, that one server stays tied up until it  
gets its response from the database (which it no longer needs).

Thanks!