I'm trying to get to grips with Maypole's error handling.
There are many circumstances detected in handler_guts where the handler
just returns the status code -1 without calling send_output. This
results in the user seeing an HTTP 500 Server Error page, which I
believe is inappropriate for circumstances such as a plain page not
being found, or an authorization failure, or in fact any problem caused
by inappropriate input from the browser that Maypole has been able to
detect.
This happens with CGI, I don't know how it behaves in mod_perl?
One can argue that Maypole doesn't know what you want to do so it
doesn't guess :) but I feel it ought to at least return a sensible HTTP
response code to the browser, rather than just claiming to have died!
Certainly if I'm browsing and get a 500 from a site, it doesn't inspire
me with confidence in the website's authors. IMHO, it would also be
sensible to have some default factory templates for these cases (403,
404 etc) that users could then easily replace by adding custom templates.
Have I missed something or do other people see the same?
My current plan is to spend some time investigating and hopefully come
up with (a) some patches and (b) a section for the docs that explains
error handling.
Cheers, Dave
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.298 / Virus Database: 265.6.5 - Release Date: 26/12/04_______________________________________________ maypole-dev mailing list maypole-dev at lists.netthink.co.uk http://lists.netthink.co.uk/listinfo/maypole-dev
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT