Last modified: 2014-05-18 13:43:06 UTC
MediaWiki generates useful 404 pages which get caught by the proxy.
This blocks development for me currently. Django catches exceptions then displays them using an HTTP 500 page, so no content is left in error.log. However the proxy catches those HTTP 500 pages further, and replaces them with a standard error page, making me unable to see any exception details anywhere.
Yuvi, are you a maintainer of the proxy?
Talked about this with Liangent on IRC some more. Currently the nginx proxy intercepts 404s, 403s, 500s, 502s and 503s and displays helpful content instead. This is, by default, useful since it mentions the names of the maintainers. However, sometimes this is frustrating, for the use cases Liangent mentioned. The proxy should be able to check if there is any content in the HTTP body from the server upstream, and if so just pass it through rather than redirect. In addition, we should edit the default lighty config to not generate ugly 404 pages but just let them pass through with no content in the body as well. Now to actually do those things...