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

Feature request: Support TLS backends #153

Open
mhutter opened this issue May 14, 2019 · 4 comments
Open

Feature request: Support TLS backends #153

mhutter opened this issue May 14, 2019 · 4 comments

Comments

@mhutter
Copy link

mhutter commented May 14, 2019

If the app being served is a HTTPS server, gin cannot connect to it.

Proposal: Add a --tls flag to indicate that the backend is a TLS listener

@silgon
Copy link

silgon commented Jan 12, 2021

+1
Has something been done about this in the past year?
This seems rather important in order to use HTTP2 push as in the server push example. (I cannot get it to work)

@mhutter
Copy link
Author

mhutter commented Jan 13, 2021

What I usually do as a workaround in those cases:

  • use the --immediate flag
  • connect to the app directly (bypassing gin alltogether)

@silgon
Copy link

silgon commented Jan 15, 2021

Thanks for the answer @mhutter , however, I tried running:

gin run example.go --immediate

However still the same problem. I'm using the command line RunTLS(":3001", "server.crt", "server.key") which works with go run example.go but not with the above command.

@silgon
Copy link

silgon commented Jan 15, 2021

I found out about the go watch. I'm working with that for now, seems to work at least for simple files. Not sure that it could work for bigger things =)

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

2 participants