www: gzip_filter: implicitly flush {obuf} on zmore/zflush

This seems like the least disruptive way to allow more use of
->zmore when streaming large messages to sockets.

1 files changed, 5 insertions, 4 deletions

diff --git a/lib/PublicInbox/GzipFilter.pm b/lib/PublicInbox/GzipFilter.pm
index 86d34183..75ba625e 100644
--- a/lib/PublicInbox/GzipFilter.pm
+++ b/lib/PublicInbox/GzipFilter.pm
@@ -140,8 +140,8 @@ sub zmore {
         my $self = $_[0]; # $_[1] => input
         http_out($self);
         my $err;
-        for (1..$#_) {
-                $err = $self->{gz}->deflate($_[$_], $self->{zbuf});
+        for (delete $self->{obuf}, @_[1..$#_]) {
+                $err = $self->{gz}->deflate($_ // next, $self->{zbuf});
                 die "gzip->deflate: $err" if $err != Z_OK;
         }
         undef;
@@ -153,8 +153,9 @@ sub zflush ($;@) {
         my $zbuf = delete $self->{zbuf};
         my $gz = delete $self->{gz};
         my $err;
-        for (1..$#_) { # it's a bug iff $gz is undef w/ $_[1..]
-                $err = $gz->deflate($_[$_], $zbuf);
+        # it's a bug iff $gz is undef w/ $obuf or $_[1..]
+        for (delete $self->{obuf}, @_[1..$#_]) {
+                $err = $gz->deflate($_ // next, $zbuf);
                 die "gzip->deflate: $err" if $err != Z_OK;
         }
         $gz // return ''; # not a bug, recursing on DS->write failure