-----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. It's jetty, so its likely that it _could_ be fixed, but working with them is like pulling teeth. Thanks for the help. I'll start digging on both options (upgrading, or getting the backend fixed). At least now I know that its possible tofix at the nginx end if we're willing to update to latest. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEUEARECAAYFAlKDg20ACgkQsZqG4IN3sumVTQCYqc7U0biS0DuNGifoUd8BIrid 9QCeMipoeU9sqmXgCPlAvFcc4U3RL0k= =aKa2 -----END PGP SIGNATURE----- _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
