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

Clarify "up to a reasonable number of redirect hops" for Handle HTTPS resolution support #359

Open
DeepMac opened this issue Oct 24, 2024 · 0 comments

Comments

@DeepMac
Copy link

DeepMac commented Oct 24, 2024

Regarding:

HTTP redirects (eg, 301, 302) are allowed, up to a reasonable number of redirect hops.

There is no set maximum number of hops for HTTP redirects, and different browsers implement different numbers before declaring an infinite redirect. Recommend clarifying what specifically is acceptable within atproto.

https://www.rfc-editor.org/rfc/rfc2616#section-10.3 indicates previous max of five was recommended but removed. This is a solid number and I recommend it.

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

No branches or pull requests

1 participant