Blank Pages

[Friscia, Michael]

I’m wondering if there’s a simple way to solve this problem.

The upstream application sometimes returns a blank 500 error which Nginx then serves as the blank page. This is working as intended. But what I’d like Nginx to do is display a custom error page if the upstream 500 error is blank, but if the upstream 500 page is not blank, then I want to serve the upstream 500 error page.

Has anyone ever come up with a way to handle a case like that?

I was thinking of having a custom header in the upstream app and if that header doesn’t exist, then serve a page from Nginx but before I run down that path I thought I’d ask. I cannot use proxy_intercept_errors on; because the upstream app serves customized 404 errors that I would lose.

___________________________________________
Michael Friscia
Office of Communications
Yale School of Medicine
(203) 737-7932 - office
(203) 931-5381 - mobile
http://web.yale.edu<http://web.yale.edu/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20180515/bac3b949/attachment.html>