users@jersey.java.net

[Jersey] Jersey breaks compatibility with reverse proxies (nginx) when tracing headers are on

From: Van Klaveren, Brian N. <bvan_at_slac.stanford.edu>
Date: Thu, 7 May 2015 00:00:35 +0000

Hi,

I'm testing out nginx 1.6 as a reverse proxy frontend for several Tomcat servers.

I've noticed that, when enabled, the X-Jersey-Tracing appear to break nginx, resulting in a 502-Bad Gateway on every request. I'm not sure if this is an nginx limitation or configuration issue on my part.

Has anyone else seen this issue or have any recommendations?

Brian