I was seriously looking at this. I hit a further problem. Net::HTTP parses the hostname:port combination which of course clashes with the IPv6 syntax. However as that is a problem not specific to Net::HTTP but rather is a general IPv6 issue, there is a convention to deal with that. You can use [] around an IPv6 address to use it where you would use a hostname. So it is still doable however I ran out if time to look at it myself and there is a danger of moving way from how upstream will eventually handle it. Also these things are working their way through the perl5 upstream so it may yet go up the priority list for the LWP upstream.
On 18/06/11 13:04, Maximilian Gass wrote: > On Thu, Mar 17, 2011 at 09:51:46PM +0000, Nicholas Bamber wrote: >> Consulting with verious perl people it seems that using >> IO::Socket::IP or IO::Socket::INET6 instead of IO::Socket::INET >> inside Net::HTTP should work. I have not so far been able to >> persuade upstream to try this largely because neither of those >> modules have a good record on windows. > > If they are problematic on Windows and upstream is unwilling to fix > this, can't we patch it in? -- Nicholas Bamber | http://www.periapt.co.uk/ PGP key 3BFFE73C from pgp.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
