-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Jenkins 2.0 in docker container (jenkinsci/jenkins:2.0) on CentOS7, apache (httpd-2.4.6-40.el7)
I've got Jenkins 1.656 running in a Docker container behind an Apache reverse proxy. Apache does the SSL termination. Everything works OK.
When I run the 2.0 container, everything seems to work, except that some links (probably in scripts, when redirecting to another page) revert to http:// instead of https://.
For instance, when in the configuration screen, I point at 'manage nodes', the link is correct. However, when I click it, I get a 400 error message:
"Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please."
The address bar shows I've indeed been directed to a http: url.
Edit: I need to add that I'm accessing Apache over a non-standard port, 8443, so the external URL is https://jenkins.internal.domain:8443. Internally, I'm using -env JENKINS_OPTS="-httpPort=8080" on the docker run command. The 8443 is preserved.