On 8 Feb 2000, Randal L. Schwartz wrote:
>
> 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?
can't use a coderef, because the data is stored as a string in the
http_core module's per_dir_config. you could probably pull a trick using
pnotes and a custom_response uri who knows to dig the code ref out of
pnotes.
>
> 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?
can't use a coderef, because the data is stored as a string in the
http_core module's per_dir_config. you could probably pull a trick using
pnotes and a custom_response uri who knows to dig the code ref out of
pnotes.