Bug #98024 for XML-LibXML: load_xml( location => https ) fails

Thu Aug 14 17:26:38 2014 martin.renvoize [...] ptfs-europe.com - Ticket created

Subject:	load_xml( location => https ) fails
Date:	Thu, 14 Aug 2014 09:30:04 +0100
To:	bug-XML-LibXML [...] rt.cpan.org
From:	"Renvoize, Martin" <martin.renvoize [...] ptfs-europe.com>

It would appear that loading a file located at a https url using load_xml fails with a 'file not found' error. I believe this may have something to do with not handling certificates correctly though this is only a hunch, and I'm relatively sure this has worked in the recent past? Perl Version 5.14.2 OS Debian Wheezy Module version: libxml-libxml-perl 2.0001+dfsg-1 Martin Renvoize Software Engineer, PTFS Europe Ltd Content Management and Library Solutions Skype: Landline: 0203 286 8685 Mobile: 07725985636 http://www.ptfs-europe.com

Sat Sep 14 15:24:27 2019 jmac [...] jmac.org - Correspondence added

I suspect that this is a problem with libxml2, and not with XML::LibXML per se. Evidence I've collected that suggests that libxml2 simply doesn't support https-based URLs: https://stackoverflow.com/a/57328510 https://bugzilla.gnome.org/show_bug.cgi?id=791220 So, I feel doubtful that XML::LibXML can do much about this, other than note it in its own documentation. (And I plan to submit a doc patch to this end, presently.)

Sat Sep 14 15:24:28 2019 The RT System itself - Status changed from 'new' to 'open'

Sat Sep 14 15:39:01 2019 SREZIC [...] cpan.org - Correspondence added

On 2019-09-14 15:24:27, JMAC wrote: Show quoted text

> I suspect that this is a problem with libxml2, and not with > XML::LibXML per se. > > Evidence I've collected that suggests that libxml2 simply doesn't > support https-based URLs: > > https://stackoverflow.com/a/57328510 > > https://bugzilla.gnome.org/show_bug.cgi?id=791220 >

Here another bugreport about libxml2 not supporting https: https://rt.cpan.org/Ticket/Display.html?id=124573 Show quoted text

> So, I feel doubtful that XML::LibXML can do much about this, other > than note it in its own documentation. (And I plan to submit a doc > patch to this end, presently.)