Apache-DebugInfo
view release on metacpan or search on metacpan
DebugInfo.pm view on Meta::CPAN
910911912913914915916917918919920921922923924925926927928929930Calling Apache::DebugInfo methods
with
'https://metacpan.org/pod/PerlHandler">PerlHandler'
as an argument
has
been disabled - doing so gets your headers and script printed
to the browser, so I thought I'd save the unaware from potential
pitfalls.
Phase misspellings, like
'PelrInitHandler'
pass through without
warning, in case you were wondering where your output went...
The get_handlers and mark_phases methods are incomplete, mainly due to
oversights in the mod_perl API. Currently (as of mod_perl 1.2401),
they cannot function properly on the following callbacks:
PerlInitHandler
As such, they have been disabled
until
forthcoming corrections to the
API can be implemented. PerlHeaderParserHandlers and
PerlPostRequestHandlers function normally.
The output uri is whatever the uri was
when
new() was called (either
on the fly or in Apache::DebugInfo::handler). Thus
if
the uri
has
undergone translation since the new() call the original, not the new,
uri will be output. This feature can be easily remedied, but having a
changing uri in the output may be confusing
when
debugging. Future
177178179180181182183184185186187188189190191192193194195196197Calling Apache::DebugInfo methods
with
'https://metacpan.org/pod/PerlHandler">PerlHandler'
as an argument
has
been disabled - doing so gets your headers and script printed
to the browser, so I thought I'd save the unaware from potential
pitfalls.
Phase misspellings, like
'PelrInitHandler'
pass through without
warning, in case you were wondering where your output went...
The get_handlers and mark_phases methods are incomplete, mainly due to
oversights in the mod_perl API. Currently (as of mod_perl 1.2401),
they cannot function properly on the following callbacks:
PerlInitHandler
As such, they have been disabled
until
forthcoming corrections to the
API can be implemented. PerlHeaderParserHandlers and
PerlPostRequestHandlers function normally.
The output uri is whatever the uri was
when
new() was called (either
on the fly or in Apache::DebugInfo::handler). Thus
if
the uri
has
undergone translation since the new() call the original, not the new,
uri will be output. This feature can be easily remedied, but having a
changing uri in the output may be confusing
when
debugging. Future
( run in 0.332 second using v1.01-cache-2.11-cpan-00829025b61 )