Re^3: How to remove HTTP Keep-Alive 300 header from LWP::UserAgent request

in reply to Re^2: How to remove HTTP Keep-Alive 300 header from LWP::UserAgent request
in thread How to remove HTTP Keep-Alive 300 header from LWP::UserAgent request

The actual code that adds the header is in Net::HTTP::Methods, at line 180 in the current version.

    if ($self->keep_alive) {
        if ($peer_ver eq "1.0") {
            # from looking at Netscape's headers
            push(@h2, "Keep-Alive: 300");
            unshift(@connection, "Keep-Alive");
        }
    }
[download]

So, I would guess that Net::HTTP believes your connection is http/1.0, and is therefore sending the http/1.0 header. If it's not, maybe you can make a bug report against the module?

Comment on Re^3: How to remove HTTP Keep-Alive 300 header from LWP::UserAgent request Download Code

Replies are listed 'Best First'.
Re^4: How to remove HTTP Keep-Alive 300 header from LWP::UserAgent request by Veltro (Hermit) on May 01, 2018 at 22:04 UTC
Thanks for pointing that out to me. I already found a way to change extra options before and I managed to combine the information that you gave me into this solution: `use LWP::Protocol::http ; push(@LWP::Protocol::http::EXTRA_SOCK_OPTS, PeerHTTPVersion => 1.1) ;` [download] and addding the Connection header to ns_headers: `my @ns_headers = ( 'Connection' => 'Keep-Alive', ... }` [download]	[reply] [d/l] [select]
Re^4: How to remove HTTP Keep-Alive 300 header from LWP::UserAgent request by Anonymous Monk on Apr 27, 2018 at 02:28 UTC
So, I would guess that Net::HTTP believes your connection is http/1.0, and is therefore sending the http/1.0 header. If it's not, maybe you can make a bug report against the module? Hi, For what purpose? What would it solve?	[reply]

In Section Seekers of Perl Wisdom