Page MenuHomePhabricator

Web proxy on Cloud VPS should give a more helpful error page for 502 errors
Open, LowPublic

Description

Right now if a web proxy leads to a web server that is down, you get a very terse and unhelpful error message: "502 Bad Gateway". Arbitrary example: http://nemobis.wmflabs.org/

Contrast this with Toolforge, which provides much more descriptive error messages for tools that don't exist or tools that do exist but their webservice is down.

Event Timeline

I think we can do a proxy_intercept_errors on; and error_page 502 /path/to/some/useful/error.html; in modules/dynamicproxy/templates/domainproxy.conf, but I just went onto novaproxy-02 to see if I could safely try it out there (the active server is novaproxy-01) and found that I'm not on the sudoers list there, and don't want to step on anyone's toes by adding myself.
What should the error say? "This is a registered web proxy but the proxy cannot successfully communicate with the specified backend."?

Mentioned in SAL (#wikimedia-cloud) [2018-07-29T04:13:07Z] <zhuyifei1999_> recursively chown /data/project/pywikibot/public_html{,.old}/core/ to tools.pywikibot T200616

bd808 renamed this task from Web proxy on Cloud VPS should give a more helpful error to Web proxy on Cloud VPS should give a more helpful error page for 502 errors.Feb 10 2019, 11:07 PM