Paging methods called with negative values returns too much data

What steps will reproduce the problem?
Open up a browser window and paste the following URL in the address bar:
http://www.dotnetkicks.com/services/json/jsonservices.ashx/getFrontPageStor
iesPaged?pageNumber=-1&pageSize=-1

What is the expected output? 
At least an error if not assumption of some reasonable default in place of 
the negative values once the call reaches the server.

What do you see instead?
Some 2MB worth of story data is sent downstream in JSON. On a broadband 
connection it took about 30 seconds to download, which probably also ties 
up the server-side thread for that much time. The thread pool could easily 
be drained this way!

Original issue reported on code.google.com by azizatif on 4 Oct 2007 at 10:39

Letractively / dotnetkicks

Paging methods called with negative values returns too much data #145