On Thu, Jul 14, 2011 at 4:44 AM, Brane F. Gračnar
wrote:
> I guess your only option is nginx, which supports https upstreams.
I mentioned this earlier, but you can use stunnel in "client" mode to
connect to a remote https server.
It's unfortunate that nginx doesn't yet support http/1.1 in proxy
On Thursday 14 of July 2011 05:10:44 James Bardin wrote:
> > Some IT contracts suck. ;)
>
> Yes, they do :)
I guess your only option is nginx, which supports https upstreams. You can
nginx use nginx_http_upstream_fair
(http://wiki.nginx.org/HttpUpstreamFairModule) module to achieve fair load
d
On Wed, Jul 13, 2011 at 8:20 PM, Craig wrote:
>> I'm not sure if you're serious or not, but If another party as
>> administrating the backend servers, it seems likely that you won't
>> have the private key for the ssl certificate.
>
> Yea I am, I would't dare to write shitty semi-joke mails on Wi
Hi,
> On Wed, Jul 13, 2011 at 5:57 PM, Craig wrote:
>
>> I hereby request the feature to do https to backends
>> Sometimes it's really troublesome not being able to do that, even more
>> so if a different party administrates the servers.
>
> I'm not sure if you're serious or not, but If ano
On Wed, Jul 13, 2011 at 5:57 PM, Craig wrote:
> I hereby request the feature to do https to backends
> Sometimes it's really troublesome not being able to do that, even more
> so if a different party administrates the servers.
>
I'm not sure if you're serious or not, but If another party as
Hi,
> No. You terminate the ssl at the load-balancer, and send the http to
> the backend. You need to configure the backend servers to accept and
> trust the http traffic from the LB.
I hereby request the feature to do https to backends
Sometimes it's really troublesome not being able to do t
On Wed, Jul 13, 2011 at 11:04 PM, Christopher Ravnborg
wrote:
> Hi
> I'm looking for a solution which can do the following:
> Client need to connect to https webserver via haproxy. Encryption all the
> way.
> Log on webserver needs to contain client ip, this can be done, at least on
> http with fo
HI Christopher,
As soon has the stream exit stunnel it is in plain http, then haproxy
analyse the tthp protocol and it wil proxy the request to the http server
not the https.
if you don't use stunnel and use only haproxy you will loose all the
flexibility of haproxy because https in not yet fully
On Wed, Jul 13, 2011 at 5:04 PM, Christopher Ravnborg
wrote:
> Hi
> I'm looking for a solution which can do the following:
> Client need to connect to https webserver via haproxy. Encryption all the
> way.
You can't read the https stream, because it's encrypted.
> Log on webserver needs to cont
Hi
I'm looking for a solution which can do the following:
Client need to connect to https webserver via haproxy. Encryption all the
way.
Log on webserver needs to contain client ip, this can be done, at least on
http with forwardfor, that works fine.
I have setup haproxy and read about stunnel wit
10 matches
Mail list logo
