algorithm.
-Sam.
From: Trevor Vardeman
[mailto:trevor.varde...@rackspace.com<mailto:trevor.varde...@rackspace.com>]
Sent: Thursday, April 24, 2014 7:26 PM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [Neutron][LBaaS] Use Case Qu
enstack.org>
Subject: [openstack-dev] [Neutron][LBaaS] Use Case Question
Hey,
I'm looking through the use-cases doc for review, and I'm confused about one of
them. I'm familiar with HTTP cookie based session persistence, but to satisfy
secure-traffic for this case would there b
ailto:trevor.varde...@rackspace.com]
> *Sent:* Thursday, April 24, 2014 7:26 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [Neutron][LBaaS] Use Case Question
>
>
>
> Hey,
>
>
>
> I'm looking through the use-cases doc for review, and
@lists.openstack.org
Subject: [openstack-dev] [Neutron][LBaaS] Use Case Question
Hey,
I'm looking through the use-cases doc for review, and I'm confused about one of
them. I'm familiar with HTTP cookie based session persistence, but to satisfy
secure-traffic for this case would there be decryp
I mis quoted it should be in RFC 5246 not 5264.
On Apr 25, 2014, at 2:50 AM, Carlos Garza
mailto:carlos.ga...@rackspace.com>> wrote:
Trevor is referring to our plans on using the SSL session ID of the
ClientHello to provide session persistence.
See RFC 5264 section 7.4.1.2 which sends an
On 04/25/2014 12:50 AM, Carlos Garza wrote:
> Trevor is referring to our plans on using the SSL session ID of the
> ClientHello to provide session persistence.
> See RFC 5264 section 7.4.1.2 which sends an SSL session ID in the clear
> (Unencrypted) so that a load balancer with out the decryp
Trevor is referring to our plans on using the SSL session ID of the
ClientHello to provide session persistence.
See RFC 5264 section 7.4.1.2 which sends an SSL session ID in the clear
(Unencrypted) so that a load balancer with out the decrypting key can use it to
make decisions on which
back
Hi Trevor,
If the use case here requires the same client (identified by session
cookie) to go to the same back-end, the only way to do this with HTTPS is
to decrypt on the load balancer. Re-encryption of the HTTP request may or
may not happen on the back-end depending on the user's needs. Again, i
Hey,
I'm looking through the use-cases doc for review, and I'm confused about one of
them. I'm familiar with HTTP cookie based session persistence, but to satisfy
secure-traffic for this case would there be decryption of content, injection of
the cookie, and then re-encryption? Is there anoth
