Interesting. That did the trick actually. So this test code...

     my $test_header = $cgi->header(
         -type => 'application/xml'
     );

     ddump('test_header', __LINE__, $test_header);

     my $another_test_header = $cgi->header(
         -nph => 1,
         -type => 'application/xml'
     );

     ddump('another_test_header', __LINE__, $another_test_header);
[download]

...produced the following debug output...

$test_header_line_673_1 = '';
$another_test_header_line_680_1 = 'HTTP/1.1 200 OK
Server: Apache/2.4.34 (Red Hat) OpenSSL/1.0.2k-fips mod_perl/2.0.11 Pe
+rl/v5.22.4
Date: Wed, 07 Oct 2020 21:53:46 GMT
Content-Type: application/xml; charset=ISO-8859-1

';
[download]

Congratulations, Andy, and thanks for sharing the detailed test code and output. I haven't used ddump but that aspect of your post is very helpful and interesting to me.

Sorry the late reply. :)

ddump() is just my own silly little Data::Dumper wrapper. While I like and use Ovid's module Data::Dumper::Names frequently, it can't work everywhere.

# {{{ ddump
#
sub ddump
{

    my $label       = shift;
    my $line_number = shift;

    my $ddv = $Data::Dumper::Varname;

    $Data::Dumper::Varname = "${label}_line_${line_number}_";

    print STDERR Dumper(@_);

    $Data::Dumper::Varname = $ddv;

}

# }}}
[download]

Definitely nothing special there...

--
Andy

Interesting. I wonder what that nph (no parsed header) business ends up doing... I'll have to experiment with that.

Thanks!