Skip Menu |

This queue is for tickets about the libwww-perl CPAN distribution.

Report information
The Basics
Id: 98782
Status: resolved
Priority: 0/
Queue: libwww-perl

Owner: Nobody in particular
Requestors: james.thomas [...]
Cc: gregoa [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

Subject: CONNECT request URL different in 6.05 and 6.08
Date: Thu, 11 Sep 2014 11:26:49 +0100
To: bug-libwww-perl [...]
From: James Thomas <james.thomas [...]>
Download (untitled) / with headers
text/plain 1.4k
_version_ Linux 2.6.18-308.1.1.el5xen #1 SMP Wed Mar 7 04:57:35 EST 2012 x86_64 x86_64 x86_64 GNU/Linux This is perl, v5.10.1 (*) built for x86_64-linux _observed_ I have found that CONNECT requests are different depending on whether libwww-perl 6.05 or libwww-perl 6.08 is used: ---- #!/usr/bin/env perl use strict; use Data::Dumper; use LWP::UserAgent; my $ua=LWP::UserAgent->new(keep_alive=>1); my $request = HTTP::Request->new(CONNECT => ""); my $response=$ua->request($request); print Dumper $response; ---- And these are the requests submitted by them, captured with tcpdump and viewed in wireshark. Note the different URL and the corresponding different response. I noticed this on local servers after a recent upgrade to 6.08 on one of our clients. We have been running libwww-perl 6.02 and 5.833 locally for a long time. I note that there have been changes in an apparently related area in but I haven't attempted to debug it in detail. _exhibits_ I'm attaching * google_test.txt - console output for two runs of the given script * http.pcap - the tcpdump capture for two runs of the given script -- James Thomas Linguamatics Ltd 324 Cambridge Science Park Milton Road Cambridge CB4 0WG UK Tel: +44 1223 651910 Fax: +44 1223 654869 URL:
Download giaafife.png
image/png 20.4k
Download http.pcap
application/octet-stream 5.2k

Message body not shown because it is not plain text.

Download google_test.txt
text/plain 3.7k

Message body is not shown because sender requested not to inline it.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to