David Dick wrote:
If I'm correct both Apache::PerlRun and Apache::Registry will have
problems in certain situations if we agree that ModPerl::Registry has
the correct logic for handling the execution status. If you can tell
otherwise please give me a test script that doesn't work under
ModPerl::R
If I'm correct both Apache::PerlRun and Apache::Registry will have
problems in certain situations if we agree that ModPerl::Registry has
the correct logic for handling the execution status. If you can tell
otherwise please give me a test script that doesn't work under
ModPerl::Registry.
But in yo
David Dick wrote:
alrightly, back again. The problem is that Apache::Registry will return
a 206, which will trigger the error message. In case there is anyone
out there as daft as me :), the crude delegation-type module below can
solve this problem. Maniacs who see a need to return 204's, et
alrightly, back again. The problem is that Apache::Registry will return
a 206, which will trigger the error message. In case there is anyone
out there as daft as me :), the crude delegation-type module below can
solve this problem. Maniacs who see a need to return 204's, etc can
probably ext
Hi again,
On Mon, 3 Feb 2003, David Dick wrote:
> not even getting a broken connection. So somehow mod_perl doesn't
> _really_ think it's an error.
Check out DEBUGGING in 'perldoc Apache::Registry'.
Apache::Registry won't always return what you'd think it should.
This has snookered more than
not even getting a broken connection. So somehow mod_perl doesn't
_really_ think it's an error.
Ged Haywood wrote:
Hi there,
On Sun, 2 Feb 2003, David Dick wrote:
Forgot to mention that the error log is completely empty. :)
Are you getting core dumps?
73,
Ged.
Hi there,
On Sun, 2 Feb 2003, David Dick wrote:
> Forgot to mention that the error log is completely empty. :)
Are you getting core dumps?
73,
Ged.
Good Point. Forgot to mention that the error log is completely empty. :)
Ged Haywood wrote:
Hi there,
On Sun, 2 Feb 2003, David Dick wrote:
Got a bit of a weird set of behaviour with a mod_perl Apache::Registry
type script.
[snip]
More information about this error may be available
Hi there,
On Sun, 2 Feb 2003, David Dick wrote:
> Got a bit of a weird set of behaviour with a mod_perl Apache::Registry
> type script.
[snip]
> More information about this error may be available
> in the server error log.
[snip]
> Anyone got any ideas?
What does it say in the error_log?
73,
G
G'day all,
Got a bit of a weird set of behaviour with a mod_perl Apache::Registry
type script.
HISTORY:
I've been using MD5 digests of the html sent from my scripts as ETags,
hence saving an important bit of bandwidth. Got a little bit carried
away with the success of this project and attempte
10 matches
Mail list logo