blacklightcms
Updates "link" header access in `populatePageCursor` to be case-insensitive
Recurly's API recently updated the casing of some response headers. While this doesn't affect this client library at all right now, there is no guarantee that any response header's casing will be the same going forward.
The only header that's accessed in a case-sensitive manner is the "Link" header in the populatePageCursor function. Right now, this works fine, as the "Link" response header hasn't been changed, but this isn't guaranteed to stay this way in the future (see HTTP 1.1 RFC 2616, which states that "field-names are case insensitive" for more info on this).
I'd be happy to add an assertion for this as well if it's helpful! Please feel free to respond in the PR or reach out if you have any questions, concerns, or anything at all.
