| Harej | |
| Jul 28 2018, 6:23 PM |
| F37720502: image.png | |
| Sep 14 2023, 8:40 AM |
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.
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| dynamicproxy: improve connection error pages | Majavah | operations/puppet | production | +49 -13 |
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
Change 957254 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] dynamicproxy: improve connection error pages
Change 957254 merged by Majavah:
[operations/puppet@production] dynamicproxy: improve connection error pages
