You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After update Net-HTTP from 6.03 to 6.05 VMware-vSphere-Perl-SDK does not
work
I get
SOAP request error - possibly a protocol issue: <?xml version="1.0"
encoding="UTF-8"?>
For 6.03 all worked fine.
I use FreeBSD 8.2-RELEASE. Not tested for another OSes.
# perl -v
This is perl 5, version 12, subversion 4 (v5.12.4) built for
i386-freebsd-64int
How-to-repeat:
e.g.
/usr/local/share/examples/vmware-vsphere-cli/performance/viperformance.pl --host
XX.XX.XX.XX --server XX.XX.XX.XX --countertype net --samples 1
--instance "*" --username root --password XXXXXXXXX
Net-HTTP 6.06 might fix the bug when using IO::Socket::SSL but vmware is
using Crypt::SSLeay.
A similar fix for Net::SSL is required, the problem is that Net::SSL do not
yet have the pending method, it should be added, returning the value of
SSL_pending.
The correct fix is probably:
return 1 if $self->can('pending') && $self->pending;
and ask the Net::SSL maintainer to add the pending method.
Net::HTTP-6.04 and newer are not compatible with Net::SSL
Net::SSL2.86 add the 'pending' method.
The attached patch fix Net:HTTP to use the pending method of Net:SSL.
A new release with this patch will be appreciated by all vmware users,
downgrading LWP and Net::SSL will no longer be required.
Jean-Louis
On Thu Apr 24 17:31:49 2014, [email protected] wrote:
>
> A new release with this patch will be appreciated by all vmware users,
> downgrading LWP and Net::SSL will no longer be required.
This patch doesn't work for me to fix the VMware Perl SDK. What does work is to remove the parts in VICommon.pm that explicitly require Net::SSL or Crypt::SSLeay.
The text was updated successfully, but these errors were encountered:
Migrated from rt.cpan.org#81684 (status was 'open')
Requestors:
Attachments:
From [email protected] on 2012-12-04 07:40:22
:
From [email protected] on 2013-04-19 15:29:39
:
From [email protected] on 2013-09-11 18:57:00
:
From [email protected] on 2014-04-24 21:31:49
:
From https://www.google.com/accounts/o8/id?id=AItOawmgj_ZwMoFVbbbACmIegfUp5mGrRAE9rHA on 2014-10-23 22:50:51
:
The text was updated successfully, but these errors were encountered: