-
Notifications
You must be signed in to change notification settings - Fork 375
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
feat: remove SafeRoundTripper
and allow private-IP HTTP connections
#1152
Conversation
071ae1c
to
cc01c53
Compare
Looks like the test is failing because it's still referencing a variable that was removed in this PR. |
cc01c53
to
08dece3
Compare
08dece3
to
f1e9be7
Compare
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.
LGTM!
@hf fwiw, i dont think this will resolve the issue because we use netlify's mailme under the hood which imports the netlify http commons package: https://github.com/netlify/mailme/blob/876c043aa349526e4372914d5ee416ec1de242f1/mailme.go#L120 |
also i think we should update the description in the PR and unlink the issue to avoid confusion |
…supabase#1152) Removes `SafeRoundTripper` which was a HTTP `RoundTripper` which did not allow establishing HTTP connections to servers listening on private IP addresses. This is probably inherited from the Netlify codebase, and was added as a safeguard to avoid cyclic requests with their hooks implementation which is not used by Supabase. Why it's absolutely normal to expect connections to private IP addresses: - Running GoTrue in Kuberenetes, AWS ECS, or other places. - Local development with Docker, which loves to create virtual private networks inside containers all the time. - Caches inside VPCs. - Rendering templates served only within the VPC and not those that are publicly available.
…supabase#1152) Removes `SafeRoundTripper` which was a HTTP `RoundTripper` which did not allow establishing HTTP connections to servers listening on private IP addresses. This is probably inherited from the Netlify codebase, and was added as a safeguard to avoid cyclic requests with their hooks implementation which is not used by Supabase. Why it's absolutely normal to expect connections to private IP addresses: - Running GoTrue in Kuberenetes, AWS ECS, or other places. - Local development with Docker, which loves to create virtual private networks inside containers all the time. - Caches inside VPCs. - Rendering templates served only within the VPC and not those that are publicly available.
…supabase#1152) Removes `SafeRoundTripper` which was a HTTP `RoundTripper` which did not allow establishing HTTP connections to servers listening on private IP addresses. This is probably inherited from the Netlify codebase, and was added as a safeguard to avoid cyclic requests with their hooks implementation which is not used by Supabase. Why it's absolutely normal to expect connections to private IP addresses: - Running GoTrue in Kuberenetes, AWS ECS, or other places. - Local development with Docker, which loves to create virtual private networks inside containers all the time. - Caches inside VPCs. - Rendering templates served only within the VPC and not those that are publicly available.
Removes
SafeRoundTripper
which was a HTTPRoundTripper
which did not allow establishing HTTP connections to servers listening on private IP addresses.This is probably inherited from the Netlify codebase, and was added as a safeguard to avoid cyclic requests with their hooks implementation which is not used by Supabase.
Why it's absolutely normal to expect connections to private IP addresses: