Bug 1430863

Description of problem:

There is an application [1] deployed on evg dedicated cluster in two ways:

* pre-build Docker image [2]
* s2i using EAP [3]

the pre-build container is deployed using:

```
oc new-app docker.io/osevg/workshopper:ui -e WORKSHOPS_URLS="http://workshopper.pixy.io/export/a8ce3820425f41caa843e0e1842b8a70" -e CONTENT_URL_PREFIX="https://raw.githubusercontent.com/osevg/workshopper-content/master/" --name work
oc expose svc work
```

when user tries to load the page (tested on at least 4 different connections)
the requests are randomly responded with 503 errors by the haproxy. When using the same image
on localhost I do not see this behaviour.

[1] https://github.com/osevg/workshopper
[2] http://work-workshopper.e203.evg.openshiftapps.com/
[3] http://workshopper-workshopper.e203.evg.openshiftapps.com/

Version-Release number of selected component (if applicable):
OpenShift Master is v3.4.1.7

How reproducible:
intermittent, but very often

Steps to Reproduce:
1. View route URL from [2] or [3] and view request responses in browser
2. 
3.

Actual results:
Either route request itself will result in 503 or component requests (.css, .js) will return 503, for example, from Chrome console:

'http://work-workshopper.e203.evg.openshiftapps.com/css/coreui.css Failed to load resource: the server responded with a status of 503 (Service Unavailable)'

routes/resources that fail are not consistent with each page reload.

Expected results:
No 503s - route and component requests should resolve properly.

Additional info: