Hi,
On 20/03/2012 11:52, Wilfred Springer wrote:
It turns out that mod_proxy is dropping the 'n' header on its way out. I
tried a number of things to make sure it's getting preserved, but it
isn't. After that, I tried nginx. On the plus side, nginx *does*
preserve the n header on its way out. At the other hand, now all of a
sudden Jenkins starts complaining about the reverse proxy not being
configured correctly, and apparently there is other stuff that is
missing as well with nginx support.
Is anybody using Apache or Nginx with HTTPS in front of Jenkins *at all*?
Yes. I have the same configuration working over both http and https with
Apache 2.2.
I use the following over and above the standard apache SSL configuration
(there are a few ACLs for allowing access too but they shouldn't make a
difference).
ProxyVia block
ProxyRequests off
ProxyPreserveHost on
ProxyTimeout 300
ProxyPass / http://127.0.0.1:8082/
ProxyPassReverse / http://127.0.0.1:8082/
ProxyPreserveHost On
With that Chrome reports the following headers being returned for an
ajax request on 1.455
Connection:Keep-Alive
Content-Encoding:gzip
Content-Type:text/html;charset=UTF-8
Date:Tue, 20 Mar 2012 15:45:27 GMT
Keep-Alive:timeout=15, max=96
Server:Winstone Servlet Engine v0.9.10
Transfer-Encoding:chunked
Vary:Accept-Encoding
X-Powered-By:Servlet/2.5 (Winstone/0.9.10)
n:88
Not sure if you have looked but the wiki has information on setting this up.
https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache
Regards
Richard
