Skip Menu |

This queue is for tickets about the EWS-Client CPAN distribution.

Report information
The Basics
Id: 68292
Status: resolved
Priority: 0/
Queue: EWS-Client

People
Owner: Nobody in particular
Requestors: raoul.koenig [...] aachtec.com
Cc:
AdminCc:

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



CC: Jonas Roehrlich <jonas.roehrlich [...] aachtec.com>
Subject: EWS::Client issue
Date: Wed, 18 May 2011 16:16:51 +0000
To: "bug-EWS-Client [...] rt.cpan.org" <bug-EWS-Client [...] rt.cpan.org>
From: Raoul König <raoul.koenig [...] aachtec.com>
Dear developers of EWS::Client, I tried a small example of your EWS-Interface: use EWS::Client; my $ews = EWS::Client->new({ server => '***.aachtec.com', username => '***', password => '***', }); my $entries = $ews->contacts->retrieve; print "I retrieved ". $entries->count ." items\n"; while ($entries->has_next) { print $entries->next->DisplayName, "\n"; } I ended up with Content-Type-issues. I think the response Content-Type is all right, but the EWS-Libary doesn't deal with the quotes: warning: Cannot process the message because the content type 'text/xml; charset="utf-8"' was not the expected type 'text/xml; charset=utf-8'. error: answer is not xml but `' I don't know, where to fix that, or if it is my own failure in some way. I would be happy if someone could help in on that. Thank you very much, Raoul PS: I'm using ActivePerl 5.12 on Mac OS X and MS Exchange 2010.
Hi, On Wed May 18 12:18:18 2011, raoul.koenig@aachtec.com wrote: Show quoted text
> I ended up with Content-Type-issues. > I think the response Content-Type is all right, but the EWS-Libary > doesn't deal with the quotes: > > warning: Cannot process the message because the content type > 'text/xml; charset="utf-8"' was not the expected type 'text/xml; > charset=utf-8'. > error: answer is not xml but `'
I think your diagnosis is correct. However I don't have access to an Exchange 2010 server, so as much as I'd like to help, it won't be easy for me to troubleshoot this. If this is an error from Perl about a message returned from the Exchange server, then it could be a misconfiguration of the header on the server. See this page: http://www.w3.org/International/O-HTTP-charset If it's an error returned from the server about a badly formed message sent by Perl, then it'll be more difficult. It could be a problem if you use the older Exchange 2007 XML schema files which ship with EWS::Client instead of downloading new ones. -- regards, oliver.