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

Q: HTTPS end-to-end #185

Closed
ghost opened this issue Nov 15, 2016 · 2 comments
Closed

Q: HTTPS end-to-end #185

ghost opened this issue Nov 15, 2016 · 2 comments
Labels

Comments

@ghost
Copy link

ghost commented Nov 15, 2016

I want to config fabio for [ https -> fabio:9999 -> https -> backend ]

  1. I'm able to config fabio to listen on https:9999
  2. My backend services only listen on https:4321

How can I config fabio to add route to https enabled backend that are dynamically registered to Consul?

When making a https request to fabio listening on 9999, fabio complaints about "http: proxy error: malformed HTTP response "\x15\x03\x00\x02\x02". At the same time, my backend complaints about "http: TLS handshake error from 127.0.0.1:46998: tls: first record does not look like a TLS handshake" It appears that fabio attempts to route the request to my backend using HTTP, not HTTPS, where HTTPS is expected.

Is this issue similar to #181 and #111?

SC

@magiconair
Copy link
Contributor

Https backends are only supported via the tcp+sni proxy for now

@magiconair magiconair changed the title Question: HTTPS end-to-end Q: HTTPS end-to-end Dec 5, 2016
@magiconair
Copy link
Contributor

Closing as duplicate of #181

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant