Just conceptualising... I haven't played with Squid for a while (so am rusty) but the simplest solution would probably be to catch all PHP errors somewhere in the Mediawiki code and return a 500 status error code.
Then get Squid to map that to the static error page. On the other hand throwing a "catch any sort of error" into an application isn't good practice. As Tim points out, errors can generate from all over the place and it is better to catch them explicitly. So that would be a non-trivial process. Tom On 25 May 2011 14:41, FT2 <ft2.w...@gmail.com> wrote: > As a non-tech, don't all reads (at least) pass through the squids, so we > can > identify and report in a nice way a lot of connection errors at that point? > </ignoreifnaive> > > FT2 > > > On Wed, May 25, 2011 at 2:18 PM, Tim Starling <tstarl...@wikimedia.org > >wrote: > > > There are dozens of places where error messages are generated. It's > > not trivial to replace them all. Some of them are hard-coded in > > compiled binaries, some are on the client side. > > > > The error message in question comes from DBConnectionError in > > Database.php in the MediaWiki source. It's hard-coded and the source > > would have had to have been patched. Since no database problems were > > anticipated, even if we had tried to implement your plan, we wouldn't > > have thought to patch Database.php, and the result would have been the > > same. > > > _______________________________________________ > foundation-l mailing list > foundation-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l > _______________________________________________ foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
