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

Change max redirects followed to 2 #5136

Merged
merged 1 commit into from Sep 28, 2017

Conversation

Projects
None yet
2 participants
@Gargron
Copy link
Member

commented Sep 28, 2017

I see no reason to allow more than that. Usually a redirect is HTTP->HTTPS, then maybe URL structure changed, but more than that is highly unlikely to be a legitimate use case.

Change max redirects followed to 2
I see no reason to allow more than that. Usually a redirect is
HTTP->HTTPS, then maybe URL structure changed, but more than that
is highly unlikely to be a legitimate use case.
@ykzts

ykzts approved these changes Sep 28, 2017

@Gargron Gargron merged commit d2f56d1 into master Sep 28, 2017

3 checks passed

codeclimate All good!
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@Gargron Gargron deleted the fix-max-hops branch Sep 28, 2017

rutan added a commit to rutan/mastodon that referenced this pull request Oct 11, 2017

Change max redirects followed to 2 (tootsuite#5136)
I see no reason to allow more than that. Usually a redirect is
HTTP->HTTPS, then maybe URL structure changed, but more than that
is highly unlikely to be a legitimate use case.

takayamaki added a commit to takayamaki/mastodon that referenced this pull request Oct 12, 2017

Change max redirects followed to 2 (tootsuite#5136)
I see no reason to allow more than that. Usually a redirect is
HTTP->HTTPS, then maybe URL structure changed, but more than that
is highly unlikely to be a legitimate use case.

cobodo pushed a commit to cobodo/mastodon that referenced this pull request Oct 20, 2017

Change max redirects followed to 2 (tootsuite#5136)
I see no reason to allow more than that. Usually a redirect is
HTTP->HTTPS, then maybe URL structure changed, but more than that
is highly unlikely to be a legitimate use case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.