A public-works app consumes a Cisco REST API that paginates with a Link header including rel="next". How should the client construct follow-on requests?
Select an answer to reveal the explanation.
Short Explanation
Follow the “next chapter” ribbon the librarian tucked in the book until there is no ribbon left. When the API pages with Link rel=next, call that URL; stop when next disappears.
Full Explanation
Link-header pagination advertises the next request URL via rel="next". The consumer constructs each follow-on call from that URL and ends the loop when next is missing. Stopping after one 200 or inventing paths leaves unread pages on the server.