RFC Errata
RFC 2696, "LDAP Control Extension for Simple Paged Results Manipulation", September 1999
Source of RFC: ldapext (app)See Also: RFC 2696 w/ inline errata
Errata ID: 7292
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Yogender Bhabhoria
Date Reported: 2022-12-28
Verifier Name: RFC Editor
Date Verified: 2023-01-06
Section 4. Example says:
C: SearchRequest + pagedResultsControl(3,"") -- Server responds with three entries plus an indication -- of 5 total entries in the search result and an opaque -- cooking to be used by the client when retrieving subsequent -- pages. S: SearchResultEntry S: SearchResultEntry S: SearchResultEntry S: SearchResultDone + pagedResultsControl(5, "opaque") -- Client sends an identical search request (except for -- message id), returning the opaque cooking, asking for -- the next page.
It should say:
C: SearchRequest + pagedResultsControl(3,"") -- Server responds with three entries plus an indication -- of 5 total entries in the search result and an opaque -- cookie to be used by the client when retrieving subsequent -- pages. S: SearchResultEntry S: SearchResultEntry S: SearchResultEntry S: SearchResultDone + pagedResultsControl(5, "opaque") -- Client sends an identical search request (except for -- message id), returning the opaque cookie, asking for -- the next page.
Notes:
It's a cookie that's received/sent. Instead of cookie, the RFC says cooking in two places.