Should be resolved with https://github.com/openshift/origin-server/pull/6267

Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/f3ffa5dc9483a8faf9177f2c1a16aa0207fd56c8
Set the Host header appropriately in Nginx alias configuration

Bug 1248439
https://bugzilla.redhat.com/show_bug.cgi?id=1248439

When using nginx as a routing-daemon, the host header should be set to the host provided by the request to the nginx load balancer. Otherwise, the pool_xxx host may be passed as the host header.

The host can be preserve after added the line 'proxy_set_header Host $host'. 
It is better to add it in the ssl server too.

server {
  listen 80;
  server_name www.sjboss.com.cn;
  location / {
    proxy_pass http://pool_ose_sjboss_anlidom_80;
    proxy_set_header Host $host;

  }
}

server {
  listen 443 ssl;
  #ssl_certificate_template
  #ssl_certificate_key_template
  server_name www.sjboss.com.cn;
  location / {
    proxy_pass http://pool_ose_sjboss_anlidom_80;

  }
}

Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/5929867612b46dcc21be843df7407b2fe0e5df55
Set the Host header appropriately in Nginx alias SSL configuration

Bug 1248439
https://bugzilla.redhat.com/show_bug.cgi?id=1248439

The nginx host header was added to the regular alias configuration for nginx, but should also be added to the ssl alias configuration

The fix works well, so move bug to Verified

server {
  listen 80;
  server_name www.sjboss1.com.cn.cc;
  location / {
    proxy_pass http://pool_ose_sjboss1_anlidom_80;
    proxy_set_header Host $host;
    
  }
}

server {
  listen 443 ssl;
  #ssl_certificate_template
  #ssl_certificate_key_template
  server_name www.sjboss1.com.cn.cc;
  location / {
    proxy_pass http://pool_ose_sjboss1_anlidom_80;
    proxy_set_header Host $host;
    
  }
}

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2666.html