-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2013 04:18 PM, Maxim Dounin wrote:
> If it doesn't work for you, you have another obvious option: fixing
> a backend will do the trick, too.
Yes, i think this is the optimal solution, but the back end is a
blackbox controlled by a vendor.
Hello!
On Tue, Nov 12, 2013 at 12:22:24PM -0500, Nathan wrote:
> On 11/12/2013 12:14 PM, Maxim Dounin wrote:
>
> > As of nginx 1.5.6+, there is the proxy_ssl_protocols directive
> > exacly for this kind of problems. Restricting proxy_ssl_ciphers to
> > a smaller set may help too (again, in 1.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2013 12:14 PM, Maxim Dounin wrote:
> Hello!
Hi!
>
> As of nginx 1.5.6+, there is the proxy_ssl_protocols directive
> exacly for this kind of problems. Restricting proxy_ssl_ciphers to
> a smaller set may help too (again, in 1.5.6+).
>
Hello!
On Tue, Nov 12, 2013 at 12:07:08PM -0500, Nathan wrote:
> I am working on setting up an http reverse proxy in front of a
> pre-packaged jetty server. The jetty server is a pre-configured
> application, and not very flexible.
>
> Here's the quick and dirty. I have nginx configured to lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am working on setting up an http reverse proxy in front of a
pre-packaged jetty server. The jetty server is a pre-configured
application, and not very flexible.
Here's the quick and dirty. I have nginx configured to listen on 443,
using its own SS
