Two things:
1. Isn't the Content-Range header for partial files (not sets of files). Since the spec seems to define it in terms of bytes, not arbitrary items.
2. I'd imagine you couldn't bookmark or share URL's using this method.
1. Isn't the Content-Range header for partial files (not sets of files). Since the spec seems to define it in terms of bytes, not arbitrary items.
2. I'd imagine you couldn't bookmark or share URL's using this method.
Also, I'm imagining this header approach more for API calls than for bookmarkable user-facing pages. This way the data that comes back from the server can be a clean array of results without metadata. Feels like metadata is what HTTP headers are for.