Description of problem: 503 header is missing in response when try to access a non-exist route Version-Release number of selected component (if applicable): 3.1 How reproducible: [root@ose31-master ~]# curl -vv foo.example.com * About to connect() to foo.example.com port 80 (#0) * Trying 10.66.219.224... * Connected to foo.example.com (10.66.219.224) port 80 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.29.0 > Host: foo.example.com > Accept: */* > <html><body><h1>503 Service Unavailable</h1> No server available to handle the request. </body></html> * Connection #0 to host foo.example.com left intact Steps to Reproduce: 1. curl a non-exist route 2. 3. Actual results: [root@ose31-master ~]# curl -vv foo.example.com * About to connect() to foo.example.com port 80 (#0) * Trying 10.66.219.224... * Connected to foo.example.com (10.66.219.224) port 80 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.29.0 > Host: foo.example.com > Accept: */* > <html><body><h1>503 Service Unavailable</h1> No server available to handle the request. </body></html> * Connection #0 to host foo.example.com left intact Expected results: * About to connect() to cakephp-example-case.router.default.svc.cluster.local port 80 (#0) * Trying 10.66.219.224... * Connected to cakephp-example-case.router.default.svc.cluster.local (10.66.219.224) port 80 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.29.0 > Host: cakephp-example-case.router.default.svc.cluster.local > Accept: */* > * HTTP 1.0, assume close after body < HTTP/1.0 503 Service Unavailable < Cache-Control: no-cache < Connection: close < Content-Type: text/html < <html><body><h1>503 Service Unavailable</h1> No server is available to handle this request. </body></html> * Closing connection 0 Additional info: When you create a application, deleting rc, pod, svc then curl the route, you could find 503 is in the header in response which is the expected result of customer.
*** This bug has been marked as a duplicate of bug 1283952 ***