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
Question: How to correctly configure reverse_proxy for a TLS upstream #25
Comments
willnorris
added a commit
that referenced
this issue
May 17, 2024
Implement reverseproxy.TLSTransport. We go ahead and store the provided TLSConfig object, but for now we only use it to indicate that we should use TLS. We don't actually use any of the provided values to configure the client. Fixes #25 Signed-off-by: Will Norris <will@tailscale.com>
willnorris
added a commit
that referenced
this issue
May 17, 2024
Implement reverseproxy.TLSTransport. We go ahead and store the provided TLSConfig object, but for now we only use it to indicate that we should use TLS. We don't actually use any of the provided values to configure the client. Fixes #25 Signed-off-by: Will Norris <will@tailscale.com>
we hadn't properly added TLS support for the transport. That should be fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
Thank you for this incredible project.
Consider following snippet:
Error message:
I understand that this limitation related to https://github.com/tailscale/caddy-tailscale#https-support but what would be the right syntax?
Thanks!
The text was updated successfully, but these errors were encountered: