[ https://issues.apache.org/jira/browse/COCOON-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559984#action_12559984 ]
Vadim Gritsenko commented on COCOON-2162: ----------------------------------------- I think 404 is appropriate for this case. Requested resource is indeed does not exist, and it should be up to the component user to handle it however he likes it. > [PATCH] Fix for Paginator when accessing out of bounds Pagination page > ---------------------------------------------------------------------- > > Key: COCOON-2162 > URL: https://issues.apache.org/jira/browse/COCOON-2162 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: (Undefined) > Affects Versions: 2.1.10, 2.1.11 > Reporter: Drew Buschhorn > Priority: Minor > Attachments: paginator.diff, screenshot-1.jpg > > > The Paginator transformer for apache cocoon will allow out of page-range > requests. > I've added the below logic-test into my own copy of cocoon, and that seems to > fix the problem. > Please let me know if you think 1. this is valid and 2. that it should be > placed into svn for the 2.1.x version of cocoon. > Example: > http://localhost/samples/paginator/text(5) > will return a valid empty file before patch (despite there being only 4 pages > worth of data to paginate) > after patch, returns ResourceNotFound/404. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.