nntp: simplify the long_response API

We we worked around the default range/termination conditions of
long_response in many cases to reduce calls to SQLite or Xapian.
So continue that trend and become more like the PSGI API
which doesn't force callers to specify an article range or
work inside a loop.

1 files changed, 10 insertions, 0 deletions

diff --git a/t/v2writable.t b/t/v2writable.t
index 62947351..2f839776 100644
--- a/t/v2writable.t
+++ b/t/v2writable.t
@@ -105,6 +105,7 @@ if ('ensure git configs are correct') {
 
 {
         $mime->header_set('Message-Id', '<abcde@1>', '<abcde@2>');
+        $mime->header_set('References', '<zz-mid@b>');
         ok($im->add($mime), 'message with multiple Message-ID');
         $im->done;
         my @found;
@@ -196,6 +197,15 @@ EOF
         }
         is_deeply([sort keys %lg], [sort keys %$x],
                 'XOVER and LISTGROUPS return the same article numbers');
+
+        my $xref = $n->xhdr('Xref', '1-');
+        is_deeply([sort keys %lg], [sort keys %$xref], 'Xref range OK');
+
+        my $mids = $n->xhdr('Message-ID', '1-');
+        is_deeply([sort keys %lg], [sort keys %$xref], 'Message-ID range OK');
+
+        my $rover = $n->xrover('1-');
+        is_deeply([sort keys %lg], [sort keys %$rover], 'XROVER range OK');
 };
 {
         local $ENV{NPROC} = 2;