6 Responses:

1. Reini Urban says:

   Yesterday at 2:27 pm

   I don't know why, and I cannot repro it nor had the same bitrot, but I can explain when:

   This HTTP/Headers.pm:277 warning with 6.10 will appear with an empty header value.
   Headers are processed here: $self->_sorted_field_names, the empty value you get is read at my $vals = $self->{$key};

   I debugged it like:
   perl -S -d lwp-request -E -m HEAD https://www.jwz.org/blog/2015/09/more-lwp-bit-rot/
   > b postpone HTTP::Headers::as_string
   > c
   and then when you hit it get a better breakpoint
   > b 264 !$vals
   > c
   and then you see which header is empty, with
   > x $key

   Reply
   • moof says:

     Yesterday at 11:32 pm

     And you can probably bodge around the warnings in the meantime by changing line 263 of Headers.pm from
     my $vals = $self->{$key};
     to
     my $vals = $self->{$key} // '';
     to force a defined-but-empty value to exist. (Assuming you're using perl 5.10 or higher.)

     Reply
2. Ben says:

   Yesterday at 5:32 pm

   I suspect this started with 6.08, or more specifically this commit.

   Reply
3. Zak Elep says:

   Yesterday at 9:06 pm

   By not using LWP in the first place?

   Its 2015, there are more options now, like Furl::HTTP and Mojo::UserAgent.

   Reply
   • Aaron says:

     Yesterday at 10:26 am

     Yes, let us discard old and predictable brokenness for functionally identical, yet new and exciting, brokenness! Thank God you're here.

     Reply
     • Jon says:

       21 hours ago at 2:01 pm

       Yeah. Why even Perl? New stuff has been around ... PHP... uh,.. running

       Reply