-
Notifications
You must be signed in to change notification settings - Fork 5
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
Reverse-proxying #1
Comments
this can be implemented using |
As Michael noted in this comment this would break client certificates, but there might be other solutions like SNI proxies. Thanks for the info though. |
I thought you meant more of an tls-terminating proxy where server makes request on behalf of client, similar to how if I had an https proxy, it would make a separate connection to another https resource and pass response back to client |
Yes, that is what I was thinking originally. I only brought up SNI proxies because Michael did, and I think it's an interesting solution. The end result in most cases would be the same, better even, because client certs would remain intact. |
Feature request.
Gig looks great, nice work! I was wondering if reverse-proxying is on your roadmap, so all requests under a certain route or whatever is sent to a different Gemini server.
The text was updated successfully, but these errors were encountered: