Enforce size limit when paged searches are enabled #445
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enforce size limit when paged searches are enabled
Fixes the
:sizeoption being ignored when paged searches are enabled and the requested size exceeds 126.Problem
When paging is enabled and remaining entries needed exceeds 126, the code sets
query_limit = 0(no server-side limit) to avoid conflicts with the page size. However, the limit is never enforced client-side.The existing code comment acknowledges this:
Solution
Add a client-side check to break the paging loop when the requested size limit is reached:
Related Issues
nsslapd-sizelimitis 126 #437Testing
Tested against a production LDAP server with 5900+ entries matching the filter.
Before: all 5900+ returned.
After: exactly 3000 as requested.
Checklist
lib/net/ldap/connection.rbbundle exec rake)