In situations where you have existing web sites on your server, you may find it useful to run Jenkins (or the servlet container that Jenkins runs in) behind Lighttpd.
This allows you to bind Jenkins to the part of a bigger website that you may have or centralize the TLS termination in a single place.
This section discusses some of the approaches for doing this.
The mod_proxy works
by making Lighttpd perform as a "reverse proxy".
This means when a request arrives for certain URLs, Lighttpd becomes a proxy and forwards that request to Jenkins, then forwards the response from Jenkins back to the client.
There are two alternatives to configure Jenkins with Lighttpd.
Select the technique that best meets your needs:
By default, Lighttpd will force the URL normalization, thus mismatching the headers used by an internal Jenkins reverse
proxy test.
This results in showing the message It appears that your reverse proxy setup is broken on the manage page.
To avoid this, explicit disable the option url-path-2f-decode
.