On Wed, 09 Feb 2000, Randal L. Schwartz wrote:
> >>>>> "Bill" == Bill Jones <[EMAIL PROTECTED]> writes:
>
> >> From: [EMAIL PROTECTED] (Randal L. Schwartz)
> >> The docs hint that I can use whatever I would put after ErrorDocument
> >> as the arg to custom_response, but also suggest that I can put "a
> >> module" there. Does that mean it's the same style of argument as a
> -> pushhandler(), where I can also put a coderef?
>
>
> Bill> In Chapter Nine, there are other possibilities. Would you wish to:
>
> Bill> set_handlers()
>
> No, that's not going to work. If I push a content handler, but then
> error out, it'll go to the *error* handler, not the content handler.
>
> And for those following along, after further study in the source, it
> looks like custom_response can be only one of three things: a string,
> an internal URL (internal redirect) or an external URL (external
> redirect on error). Same thing as a "ErrorDocument" directive.
>
> So, I'm punting. When I get an error, I have to redirect to a URL,
> which then has to start all over figuring out why they were sent
> there. Which is not totally bad, because I have to ask the user some
> questions in a form, and I need to reevaluate why they might be there
> on the return trip anyway in case the world has changed out from under
> me.
Can you do an internal redirect and stuff things in pnotes/notes?
--
<Matt/>
Details: FastNet Software Ltd - XML, Perl, Databases.
Tagline: High Performance Web Solutions
Web Sites: http://come.to/fastnet http://sergeant.org
Available for Consultancy, Contracts and Training.
