Bug #89783 for libwww-perl: lwp-request: -e implies -s

Fri Oct 25 20:53:15 2013 $_ = 'spro^^*%*^6ut# [...] &$%*c>#!^!#&!pan.org'; y/a-z.@//cd; print - Ticket created

Subject:

lwp-request: -e implies -s

In version 5.834, I could dump the headers without the status code using -e. In version 6.03, -e implies -s and there appears to be no way to turn it off. I don’t know when the regression was introduced. $ lwp-request5.10 -v 2>&1 | head -n 1 This is lwp-request version 5.834 (libwww-perl-5.837) $ lwp-request5.10 -m GET -e 'nntp://nntp.perl.org/000001ceab1a$29aebd20$7d0c3760$@cp.net' | head -n 3 Date: Fri, 6 Sep 2013 17:00:07 +0100 From: meta.support@cp.net ("John Unsworth - CP Meta Support") Server: you can post $ lwp-request5.12 -v 2>&1 | head -n 1 This is lwp-request version 6.03 (libwww-perl-6.03) $ lwp-request5.12 -m GET -e 'nntp://nntp.perl.org/000001ceab1a$29aebd20$7d0c3760$@cp.net' | head -n 3 200 OK Date: Fri, 6 Sep 2013 17:00:07 +0100 From: meta.support@cp.net ("John Unsworth - CP Meta Support")

Sun Oct 27 02:34:46 2013 GAAS [...] cpan.org - Correspondence added

The change was introduced in https://github.com/libwww-perl/libwww-perl/commit/339432622042ee9e34670cae852047ee0b142196 about 3 years ago (in the 6.00 release).

I might not have noticed that there was a change in behaviour for -e in that commit.

Since it's been that was for 3 years I don't think I want to change it back now.

Do you think there is value in still having the old behaviour available somehow?

Sun Oct 27 02:34:46 2013 The RT System itself - Status changed from 'new' to 'open'

Sun Oct 27 08:39:32 2013 $_ = 'spro^^*%*^6ut# [...] &$%*c>#!^!#&!pan.org'; y/a-z.@//cd; print - Correspondence added

On Sun Oct 27 02:34:46 2013, GAAS wrote: Show quoted text

> The change was introduced in > https://github.com/libwww-perl/libwww- > perl/commit/339432622042ee9e34670cae852047ee0b142196 > about 3 years ago (in the 6.00 release). > > I might not have noticed that there was a change in behaviour for -e > in that > commit. > > Since it's been that was for 3 years I don't think I want to change it > back > now. > > Do you think there is value in still having the old behaviour > available > somehow?

Yes. I can pipe it straight to MIME::Entity. With the status line present, MIME::Entity treats a multi-part document as having a single part, because it doesn’t recognise the headers. My development machine was upgraded a few months ago, and one of my scripts starting misbehaving. I have only just figured out why.

Fri Jan 31 01:41:56 2014 $_ = 'spro^^*%*^6ut# [...] &$%*c>#!^!#&!pan.org'; y/a-z.@//cd; print - Correspondence added

On Sun Oct 27 08:39:32 2013, SPROUT wrote: Show quoted text

> On Sun Oct 27 02:34:46 2013, GAAS wrote:

> > The change was introduced in > > https://github.com/libwww-perl/libwww- > > perl/commit/339432622042ee9e34670cae852047ee0b142196 > > about 3 years ago (in the 6.00 release). > > > > I might not have noticed that there was a change in behaviour for -e > > in that > > commit. > > > > Since it's been that was for 3 years I don't think I want to change > > it > > back > > now. > > > > Do you think there is value in still having the old behaviour > > available > > somehow?

> > Yes. I can pipe it straight to MIME::Entity. With the status line > present, MIME::Entity treats a multi-part document as having a single > part, because it doesn’t recognise the headers. > > My development machine was upgraded a few months ago, and one of my > scripts starting misbehaving. I have only just figured out why.

BTW, my solution here is to keep an old version of lwp-request around. I don’t want to have to do that forever.

Fri Mar 31 15:06:05 2017 olaf [...] wundersolutions.com - Correspondence added

Ticket migrated to github as https://github.com/libwww-perl/libwww-perl/issues/236

Fri Mar 31 15:06:06 2017 olaf [...] wundersolutions.com - Status changed from 'open' to 'resolved'