> -----Original Message-----
> From: Jean-Michel Hiver [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, November 25, 2001 7:43 AM
> To: [EMAIL PROTECTED]
> Subject: Apache::Registry HTTP HEAD "feature" fix ;-)
>
>
> Hi guys,
>
> As promised I have been producing a fix for Apache::Registry. The
> module is called "MKDoc::Registry" because it will be integrated in
> the piece of software I'm working on, but feel free to do
> whatever you
> want with it.
>
> A slight litte issue is that I really don't understand why
> this module
> is working at all (read the code), but it's just working
> fine... could
> you please test it and tell me what's going on?
>
> PS: On my system the file is located here:
> /usr/lib/perl5/site_perl/5.6.0/i386-linux/MKDoc/Registry.pm
>
well, you should be subclassing Apache::RegistryNG instead of
Apache::Registry - then your method calls would work :)
personally, I'm not too keen on a core patch that comes with "I don't
understand why... but it works" and this approach seems kinda kludgy
anyway...
this simple patch to Apache::write_client seems to have the desired effect.
tested with both normal CGI script and mod_perl API calls.
--Geoff
--- src/modules/perl/Apache.xs Fri Sep 28 14:43:13 2001
+++ ../apache-1.3/src/modules/perl/Apache.xs Mon Nov 26 08:46:04 2001
@@ -1166,7 +1166,7 @@
CODE:
RETVAL = 0;
- if (r->connection->aborted)
+ if (r->connection->aborted || r->header_only)
XSRETURN_IV(0);
for(i = 1; i <= items - 1; i++) {
