Hey,

to me it seems like you are confusing a few things.
You do not need to create a service that returns the 503 page. Your router 
returns the 503 page and your router is a docker image with haproxy in it. You 
need to customize you router configuration (see here: 
https://docs.openshift.org/latest/install_config/install/deploy_router.html#deploying-a-customized-haproxy-router
 ) and you need to learn how to use Haproxy. This could be helpful:
http://serverfault.com/questions/249109/howto-use-haproxy-custom-503-error-document-when-back-server-sends-503-http-code

Regards,
v

Am 2016-06-02 um 03:06 schrieb Philippe Lafoucrière:
Hi,

I'd like to display a 503 maintenance page using our default router.
The idea is to route the traffic to a specific service returning 503 pages to 
all requests, during our maintenance.
When I update the router to use this new service, I get a blank page, with:

```
HTTP/1.1 503 Service Unavailable
Date: Thu, 02 Jun 2016 01:05:49 GMT
Content-Length: 0
Content-Type: text/plain; charset=utf-8
Set-Cookie: 
OPENSHIFT_EDGE_gemnasium-staging_gemnasium-nginx-rails_SERVERID=10.1.1.68:8080 
<http://10.1.1.68:8080>; path=/; HttpOnly; Secure

```

So apparently the router is not returning the page when a 503 is hit. Anyway to 
prevent this behaviour?

Thanks


_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to