Chris Withers writes:
> Dieter Maurer wrote:
> >
> > You should be able to make "standard_error_message"s that
> > do not generate secondary errors.
> > If you fail, a crude minimal error handling should be okay
> > as a last resort.
>
> Hmmm... maybe there should be an option on
albert boulanger wrote:
>
> You should be able to make "standard_error_message"s that
> do not generate secondary errors.
> If you fail, a crude minimal error handling should be okay
> as a last resort.
>
> The Lisp system on Symbolics had both. It had a too-many-error-frame
You should be able to make "standard_error_message"s that
do not generate secondary errors.
If you fail, a crude minimal error handling should be okay
as a last resort.
The Lisp system on Symbolics had both. It had a too-many-error-frame
detector for the error reporter that u
Dieter Maurer wrote:
>
> You should be able to make "standard_error_message"s that
> do not generate secondary errors.
> If you fail, a crude minimal error handling should be okay
> as a last resort.
Hmmm... maybe there should be an option on this then? ;-)
cheers,
Chris
_
Chris Withers writes:
> John Chandler wrote:
> >
> > As already mentioned, not all errors (unfortunately) get handled by
> > standard_error_message - authorisation being the main culprit. In addition, if
> > an error occurs in a standard_error_message it'll also cause the plain, default
> >
John Chandler wrote:
>
> As already mentioned, not all errors (unfortunately) get handled by
> standard_error_message - authorisation being the main culprit. In addition, if
> an error occurs in a standard_error_message it'll also cause the plain, default
> error page to be displayed.
Hurm... I
Just catching up on my mail...
> Gaaah! I'm totally miffed/pissed/confused/sad about this.
>
> I have Zope 2.2.4, and if I go to:
> http://docwhat.gerf.org:9673/fish (an non-existant object)
> I get the HTTPResponse.py _error_html() function as called by
> notFoundError().
As already mentione
Tino Wildenhain wrote:
>
> facility for patches). This means including the error pages for
> 40x. I'm also a fan of localisated error messages as well as
> wap-alized ones ;)
Hmm... well, this seems like a good Fishbowl project for me.
Basically, that code shouldn't be tacked on the end, the er
> Like:
> http://site.org/fish
>
> It finds the keyword fish, and sees there is a legit URL:
> http://site.org/software/beta/fish
>
> And redirects it.
>
> But that'd need t ZCatalog at least.
And probably the PathHandler product to do what you want ;-)
cheers,
Chris
___
* Jason Byron ([EMAIL PROTECTED]) [001223 01:04]:
> There are two files:
> /lib/python/ZPublisher/HTTPResponse.py
> /lib/python/OFS/Application.py
>
> that contain error pages hard coded in.
>
> you get the HTTPResponse.py code for errors like:
>
> 403: 'Forbidden',
> 404: 'Not Found',
> 405: '
Hi Chris,
Chris Withers wrote:
*snip*
>
> PS: almost related, have you noticed how there's no way you can prevent Zope
> (other than hacking the source) from tacking the error message on the end of
> the HTML stream, even in production mode? Not only does this produce badly
> formed HTML, but i
> I think this is because these are standard error codes
> that have to do with the web server and they must work
> even if the object database doesn't.
>
> There must be a more detailed reason why these errors
> aren't connected to the db, but someone else will have
> to answer that one. :)
This
--- The Doctor What <[EMAIL PROTECTED]> wrote:
> Gaaah! I'm totally miffed/pissed/confused/sad about
> this.
>
> I have Zope 2.2.4, and if I go to:
> http://docwhat.gerf.org:9673/fish (an non-existant
> object)
> I get the HTTPResponse.py _error_html() function as
> called by
> notFoundError().
Gaaah! I'm totally miffed/pissed/confused/sad about this.
I have Zope 2.2.4, and if I go to:
http://docwhat.gerf.org:9673/fish (an non-existant object)
I get the HTTPResponse.py _error_html() function as called by
notFoundError().
Now, if I go to:
http://zope.org/fish
I get a nice fully custo
14 matches
Mail list logo
