Skip to content
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

fix(measurex): make sure we don't redirect loop forever #532

Merged
merged 1 commit into from
Sep 30, 2021

Conversation

bassosimone
Copy link
Contributor

@bassosimone bassosimone commented Sep 30, 2021

Checklist

Location of the issue tracker: https://github.com/ooni/probe

Description

This is the most immediate fix to the issue described by
ooni/probe#1792.

So, the logic was actually miss the increment, which
would have been noticed with proper unit testing.

Anyway, I am not sure why the loop ensues in the first
time. By looking at the headers, it seems we're passing
the headers correctly.

So, even though this fix interrupts the loop, it still
remains the question of whether the loop is legit or
whether we're missing extra logic to properly redirect.

This is the most immediate fix to the issue described by
ooni/probe#1792.

So, the logic was actually miss the increment, which
would have been noticed with proper unit testing.

Anyway, I am not sure why the loop ensues in the first
time. By looking at the headers, it seems we're passing
the headers correctly.

So, even though this fix interrupts the loop, it still
remains the question of whether the loop is legit or
whether we're missing extra logic to properly redirect.
@bassosimone bassosimone merged commit 86018ec into master Sep 30, 2021
@bassosimone bassosimone deleted the issue/1792 branch September 30, 2021 12:07
ainghazal pushed a commit to ainghazal/probe-cli that referenced this pull request Mar 8, 2022
This is the most immediate fix to the issue described by
ooni/probe#1792.

So, the logic was actually miss the increment, which
would have been noticed with proper unit testing.

Anyway, I am not sure why the loop ensues in the first
time. By looking at the headers, it seems we're passing
the headers correctly.

So, even though this fix interrupts the loop, it still
remains the question of whether the loop is legit or
whether we're missing extra logic to properly redirect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant