X-Died header appears in apache.t [rt.cpan.org #91653]

[oalders]

Migrated from rt.cpan.org#91653 (status was 'open')

Requestors:

• CHORNY@cpan.org

From chorny@cpan.org on 2013-12-25 15:13:57:

But only in first request, second request is ok. Does not depend on presence of IO::Socket::INET6.
Strawberry perl 5.16.0
Mozilla::CA 20120309
IO::Socket::INET6 2.71
IO::Socket::SSL 1.962

with diagnostic patch https://github.com/libwww-perl/lwp-protocol-https/pull/9

not ok 2
#   Failed test at t/apache.t line 22.
#                   ''
#     doesn't match '(?^:Apache Software Foundation)'
not ok 3 - no X-Died header
#   Failed test 'no X-Died header'
#   at t/apache.t line 24.
#          got: 'read failed: No such file or directory at C:/strawberry160/perl
/site/lib/LWP/Protocol/http.pm line 414.'
#     expected: undef

-- 
Alexandr Ciornii, http://chorny.net

From jdb@cpan.org on 2015-06-10 18:40:59:

On Wed Dec 25 10:13:57 2013, CHORNY wrote:
> not ok 2
> #   Failed test at t/apache.t line 22.
> #                   ''
> #     doesn't match '(?^:Apache Software Foundation)'
> not ok 3 - no X-Died header
> #   Failed test 'no X-Died header'
> #   at t/apache.t line 24.
> #          got: 'read failed: No such file or directory at

I used to see this error too, but it is now gone.  I suspect it was fixed by updating Net::HTTP with the fix for RT#104122.

You may want to update to Net-HTTP-6.09  and check if you can still reproduce this issue.

Cheers,
-Jan

From chorny@cpan.org on 2015-06-10 21:15:48:

On Wed Jun 10 14:40:59 2015, JDB wrote:
> On Wed Dec 25 10:13:57 2013, CHORNY wrote:
> > not ok 2
> > #   Failed test at t/apache.t line 22.
> > #                   ''
> > #     doesn't match '(?^:Apache Software Foundation)'
> > not ok 3 - no X-Died header
> > #   Failed test 'no X-Died header'
> > #   at t/apache.t line 24.
> > #          got: 'read failed: No such file or directory at
> 
> I used to see this error too, but it is now gone.  I suspect it was
> fixed by updating Net::HTTP with the fix for RT#104122.
> 
> You may want to update to Net-HTTP-6.09  and check if you can still
> reproduce this issue.

Checked, same error.


-- 
Alexandr Ciornii, http://chorny.net