-
Notifications
You must be signed in to change notification settings - Fork 0
fix: follow environment-document pagination Link headers #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT: maybe over protective but is it worth to continue instead of
ok?so an unrelated malformed link doesn't block the whole operation?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thought about this one a bit more. The scenario where it'd actually fire is: an upstream emits a
Linkheader value that isn't visible-ASCII (e.g. a 0x80–0xFF byte), and also emits a separate validrel="next"Link entry that we'd miss because the bad one short-circuits the parse.RFC 5988 says Link values must be ASCII, and Flagsmith's Edge API today emits one clean Link header per response — single value, no CDN in front rewriting headers. For this corner to bite, you'd need either an upstream bug or a downstream CDN injecting a malformed Link entry before the upstream's clean one. Neither is something we've seen, and Node behaves the same way (its regex match returns
nullon the same input class — silently treats it as the last page).Going to leave as
?for now and revisit if we ever do see it in the wild — adding thecontinuewould be one line, but the failure mode it guards against is hypothetical enough that I'd rather not encode "why is thiscontinue?" into the code without a concrete scenario to point at. Happy to reopen if you'd rather have it preemptively though.