I have now implemented and documented it that way in the trunk.
If ErrorPage is set to None or does not contain the raised exception, or
if the response has already been commited, then it behaves as before.
-- Chris
-
Take
Chuck Esterbrook wrote:
> I just hope Webware is uber stable when we call it 1.0.
Right, actually I did not want to make larger changes before 1.0. But in
this case, I had to make bigger changes in the mechanisms for forwarding
and catching errors anyway, in order to fix the problems reported by
Jean-François Piéronne wrote:
> Very good idea, allowing declaration of a default error page will be
> very useful.
> May be it would be also interesting to allow the declaration of
> HPPTErrorPage for application raised exceptions. For example:
>
> HTTPErrorPage = {
> 'NotFound': '/
Christoph Zwerschke wrote:
[snip]
>
> Let me know whether you think this all makes sense before I will check
> it in ;-)
>
Very good idea, allowing declaration of a default error page will be
very useful.
May be it would be also interesting to allow the declaration of
HPPTErrorPage for applicat
On 3/24/07, Christoph Zwerschke <[EMAIL PROTECTED]> wrote:
> One thing I always disliked about Webware is the static 404 error page.
...
Your proposal sounds good to me.
I just hope Webware is uber stable when we call it 1.0.
G'night,
-Chuck
-
One thing I always disliked about Webware is the static 404 error page.
First, the name '404Text.txt' is hard coded and misleading because it is
a complete HTML page (maybe it has only been the body part in older
versions, as it is still wrongly documented), so it should better be
called someth
