Change Details

Currently, our external nginx server serves a custom 502 page when the container is down, or nginx intra-container doesn't reply. But when the nginx-intra container reply, and Ruby is still loading, we have a plain 502 error. A custom 502 error page should be prepared to address such case.

Currently, our external nginx server serves a custom 502 page when the container is down, or nginx intra-container doesn't reply. But when the nginx-intra container replies, and Ruby is still loading, we have a plain 502 error. A custom 502 error page should be prepared to address such case.

Currently, our external nginx server serves a custom 502 page when the container is down, or nginx intra-container doesn't reply. But when the nginx-intra container replyies, and Ruby is still loading, we have a plain 502 error. A custom 502 error page should be prepared to address such case.