On Wednesday 18 September 2002 05:16, Graham TerMarsch wrote:
> I'm posting primarily so that someone more intimate with the innards of
> AxKit can examine it a bit further and figure out why its actually doing
> it this way. From tracing through the code a bit here, it seems that
> AxKit actually tries to serve up the document _twice_ when its cached
> (once from cache in 'run_axkit_engine', and once in 'deliver_to_browser').
> Quirk here is also that we spit out _two_ sets of HTTP headers, which
> probably isn't right either.
Are you using AxAddOutputTransformer? Then you have found a bug.
Thank you!
Please test the attached diff if it works. (Remove your patch first, of
course)
CU
J�rg
diff -u -r1.6 Cache.pm
--- lib/Apache/AxKit/Cache.pm 5 Jun 2002 23:59:19 -0000 1.6
+++ lib/Apache/AxKit/Cache.pm 18 Sep 2002 23:49:18 -0000
@@ -219,14 +219,16 @@
$r->content_type($AxKit::OrigType);
}
my ($transformer, $doit) = AxKit::get_output_transformer();
if ($doit) {
AxKit::Debug(4, "Cache: Transforming content and printing to browser");
- $r->send_http_header() unless lc($r->dir_config('Filter')) eq 'on';
- $r->print( $transformer->( $self->read() ) );
- return OK;
+ $r->pnotes('xml_string',$self->read());
+ return OK; # upstream deliver_to_browser should handle the rest
+ #$r->send_http_header() unless lc($r->dir_config('Filter')) eq 'on';
+ #$r->print( $transformer->( $self->read() ) );
+ #return OK;
}
else {
AxKit::Debug(4, "Cache: Sending untransformed content to browser");
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
