3:33 a.m.
So, in my ongoing saga getting suds working with MS Exchange 2007 (which
I'm sure you'll hear a lot more about before I'm done :) ), I hit an a
couple interesting snags.
python-ntlm seems to time out against the server when doing POST
requests (but get requests seem fine). But that's not the current
issue.
When one of my requests went through, I got back this message:
suds.WebFault: Server raised fault: 'Server was unable to process
request. ---> Input message does not conform to Simple SOAP Binding
Profile Version 1.0. Requirement R1012: A MESSAGE MUST serialize the
envelope using either UTF-8 or UTF-16 character encoding.'
I thought Suds encoded everything in UTF-8 be default. The debug output
is below:
DEBUG:suds.client:sending to (https://myserver/EWS/exchange.asmx)
message:
<SOAP-ENV:Envelope
xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/types...
xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/messa...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns1:Body>
<ns2:GetFolder>
<ns2:FolderShape>
<ns0:BaseShape>Default</ns0:BaseShape>
</ns2:FolderShape>
<ns2:FolderIds>
<ns0:DistinguishedFolderId Id="inbox"/>
</ns2:FolderIds>
</ns2:GetFolder>
</ns1:Body>
</SOAP-ENV:Envelope>
DEBUG:suds.client:headers = {'SOAPAction':
u'"http://schemas.microsoft.com/exchange/services/2006/messages/...;,
'Content-Type': 'text/xml'}
Should the fact that it's UTF-8 encoded be in the headers or request
somewhere like so:
<?xml version="1.0" encoding="UTF-8"?>
Where is the errant behavior? Me? Suds? Exchange?
j
--
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
1:42 p.m.
On 04/03/2010 03:33 AM, Joshua J. Kugler wrote:
So, in my ongoing saga getting suds working with MS Exchange 2007
(which
I'm sure you'll hear a lot more about before I'm done :) ), I hit an a
couple interesting snags.
python-ntlm seems to time out against the server when doing POST
requests (but get requests seem fine). But that's not the current
issue.
When one of my requests went through, I got back this message:
suds.WebFault: Server raised fault: 'Server was unable to process
request. ---> Input message does not conform to Simple SOAP Binding
Profile Version 1.0. Requirement R1012: A MESSAGE MUST serialize the
envelope using either UTF-8 or UTF-16 character encoding.'
I thought Suds encoded everything in UTF-8 be default. The debug output
is below:
DEBUG:suds.client:sending to (https://myserver/EWS/exchange.asmx)
message:
<SOAP-ENV:Envelope
xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/types...
xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/messa...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns1:Body>
<ns2:GetFolder>
<ns2:FolderShape>
<ns0:BaseShape>Default</ns0:BaseShape>
</ns2:FolderShape>
<ns2:FolderIds>
<ns0:DistinguishedFolderId Id="inbox"/>
</ns2:FolderIds>
</ns2:GetFolder>
</ns1:Body>
</SOAP-ENV:Envelope>
DEBUG:suds.client:headers = {'SOAPAction':
u'"http://schemas.microsoft.com/exchange/services/2006/messages/...;,
'Content-Type': 'text/xml'}
Should the fact that it's UTF-8 encoded be in the headers or request
somewhere like so:
Suds probably should be setting the content-type http header as described in ticket 251.
(https://fedorahosted.org/suds/ticket/251). Can you try and let me know if this fixes
your problem?
<?xml version="1.0" encoding="UTF-8"?>
Where is the errant behavior? Me? Suds? Exchange?
j
1:52 p.m.
On Monday 05 April 2010, Jeff Ortel elucidated thus:
On 04/03/2010 03:33 AM, Joshua J. Kugler wrote:
> So, in my ongoing saga getting suds working with MS Exchange 2007
> (which I'm sure you'll hear a lot more about before I'm done :) ),
> I hit an a couple interesting snags.
>
> python-ntlm seems to time out against the server when doing POST
> requests (but get requests seem fine). But that's not the current
> issue.
>
> When one of my requests went through, I got back this message:
>
> suds.WebFault: Server raised fault: 'Server was unable to process
> request. ---> Input message does not conform to Simple SOAP
> Binding Profile Version 1.0. Requirement R1012: A MESSAGE MUST
> serialize the envelope using either UTF-8 or UTF-16 character
> encoding.'
>
> I thought Suds encoded everything in UTF-8 be default. The debug
> output is below:
>
> DEBUG:suds.client:sending to (https://myserver/EWS/exchange.asmx)
> message:
> <SOAP-ENV:Envelope
> xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/type
>s" xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/mess
>ages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
> <SOAP-ENV:Header/>
> <ns1:Body>
> <ns2:GetFolder>
> <ns2:FolderShape>
> <ns0:BaseShape>Default</ns0:BaseShape>
> </ns2:FolderShape>
> <ns2:FolderIds>
> <ns0:DistinguishedFolderId Id="inbox"/>
> </ns2:FolderIds>
> </ns2:GetFolder>
> </ns1:Body>
> </SOAP-ENV:Envelope>
> DEBUG:suds.client:headers = {'SOAPAction':
> u'"http://schemas.microsoft.com/exchange/services/2006/messages/Get
>Folder"', 'Content-Type': 'text/xml'}
>
> Should the fact that it's UTF-8 encoded be in the headers or
> request somewhere like so:
Suds probably should be setting the content-type http header as
described in ticket 251. (https://fedorahosted.org/suds/ticket/251).
Can you try and let me know if this fixes your problem?
Weird, I use this code:
headers = {'Content-Type': 'text/xml; charset=utf-8'}
c =
suds.client.Client('file:///home/jkugler/crc/local-tools/services.wsdl',
transport=ntlm,
headers=headers)
And Suds still tells me it's only sending 'text/xml' as the type.
Leading to the same error.
DEBUG:suds.client:sending to (https://myserver/ews/exchange.asmx)
message:
<SOAP-ENV:Envelope
xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/types...
xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/messa...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns1:Body>
<ns2:GetFolder>
<ns2:FolderShape>
<ns0:BaseShape>Default</ns0:BaseShape>
</ns2:FolderShape>
<ns2:FolderIds>
<ns0:DistinguishedFolderId Id="inbox"/>
</ns2:FolderIds>
</ns2:GetFolder>
</ns1:Body>
</SOAP-ENV:Envelope>
DEBUG:suds.client:headers = {'SOAPAction':
u'"http://schemas.microsoft.com/exchange/services/2006/messages/...;,
'Content-Type': 'text/xml'}
In the failed message back from the server, it starts:
<?xml version="1.0" encoding="utf-8"?>
Is that what needs to be added?
j
> <?xml version="1.0" encoding="UTF-8"?>
>
> Where is the errant behavior? Me? Suds? Exchange?
>
> j
--
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
2:57 p.m.
On 04/05/2010 01:52 PM, Joshua J. Kugler wrote:
On Monday 05 April 2010, Jeff Ortel elucidated thus:
> On 04/03/2010 03:33 AM, Joshua J. Kugler wrote:
>> So, in my ongoing saga getting suds working with MS Exchange 2007
>> (which I'm sure you'll hear a lot more about before I'm done :) ),
>> I hit an a couple interesting snags.
>>
>> python-ntlm seems to time out against the server when doing POST
>> requests (but get requests seem fine). But that's not the current
>> issue.
>>
>> When one of my requests went through, I got back this message:
>>
>> suds.WebFault: Server raised fault: 'Server was unable to process
>> request. ---> Input message does not conform to Simple SOAP
>> Binding Profile Version 1.0. Requirement R1012: A MESSAGE MUST
>> serialize the envelope using either UTF-8 or UTF-16 character
>> encoding.'
>>
>> I thought Suds encoded everything in UTF-8 be default. The debug
>> output is below:
>>
>> DEBUG:suds.client:sending to (https://myserver/EWS/exchange.asmx)
>> message:
>> <SOAP-ENV:Envelope
>> xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/type
>> s" xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/mess
>> ages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
>> <SOAP-ENV:Header/>
>> <ns1:Body>
>> <ns2:GetFolder>
>> <ns2:FolderShape>
>> <ns0:BaseShape>Default</ns0:BaseShape>
>> </ns2:FolderShape>
>> <ns2:FolderIds>
>> <ns0:DistinguishedFolderId Id="inbox"/>
>> </ns2:FolderIds>
>> </ns2:GetFolder>
>> </ns1:Body>
>> </SOAP-ENV:Envelope>
>> DEBUG:suds.client:headers = {'SOAPAction':
>> u'"http://schemas.microsoft.com/exchange/services/2006/messages/Get
>> Folder"', 'Content-Type': 'text/xml'}
>>
>> Should the fact that it's UTF-8 encoded be in the headers or
>> request somewhere like so:
>
> Suds probably should be setting the content-type http header as
> described in ticket 251. (https://fedorahosted.org/suds/ticket/251).
> Can you try and let me know if this fixes your problem?
Weird, I use this code:
headers = {'Content-Type': 'text/xml; charset=utf-8'}
c =
suds.client.Client('file:///home/jkugler/crc/local-tools/services.wsdl',
transport=ntlm,
headers=headers)
And Suds still tells me it's only sending 'text/xml' as the type.
Leading to the same error.
DEBUG:suds.client:sending to (https://myserver/ews/exchange.asmx)
message:
<SOAP-ENV:Envelope
xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/types...
xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/messa...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns1:Body>
<ns2:GetFolder>
<ns2:FolderShape>
<ns0:BaseShape>Default</ns0:BaseShape>
</ns2:FolderShape>
<ns2:FolderIds>
<ns0:DistinguishedFolderId Id="inbox"/>
</ns2:FolderIds>
</ns2:GetFolder>
</ns1:Body>
</SOAP-ENV:Envelope>
DEBUG:suds.client:headers = {'SOAPAction':
u'"http://schemas.microsoft.com/exchange/services/2006/messages/...;,
'Content-Type': 'text/xml'}
In the failed message back from the server, it starts:
<?xml version="1.0" encoding="utf-8"?>
Is that what needs to be added?
Yup, this should probably be added too. Most servers don't seem to care but ...
Anyway, In r671, (0.4 beta) I added "<?xml version="1.0"
encoding="utf-8"?>" and updated
the default http headers so that content-type="text/xml; charset=utf-8" All my
regression
tests against my (and public) servers pass so it seems safe to make these changes. Hope
this helps.
-jeff
j
>
>> <?xml version="1.0" encoding="UTF-8"?>
>>
>> Where is the errant behavior? Me? Suds? Exchange?
>>
>> j
3:06 p.m.
On Monday 05 April 2010, Jeff Ortel elucidated thus:
On 04/05/2010 01:52 PM, Joshua J. Kugler wrote:
> On Monday 05 April 2010, Jeff Ortel elucidated thus:
>> On 04/03/2010 03:33 AM, Joshua J. Kugler wrote:
>>> So, in my ongoing saga getting suds working with MS Exchange 2007
>>> (which I'm sure you'll hear a lot more about before I'm done :)
>>> ), I hit an a couple interesting snags.
>>>
>>> python-ntlm seems to time out against the server when doing POST
>>> requests (but get requests seem fine). But that's not the
>>> current issue.
>>>
>>> When one of my requests went through, I got back this message:
>>>
>>> suds.WebFault: Server raised fault: 'Server was unable to process
>>> request. ---> Input message does not conform to Simple SOAP
>>> Binding Profile Version 1.0. Requirement R1012: A MESSAGE MUST
>>> serialize the envelope using either UTF-8 or UTF-16 character
>>> encoding.'
>>>
>>> I thought Suds encoded everything in UTF-8 be default. The debug
>>> output is below:
>>>
>>> DEBUG:suds.client:sending to (https://myserver/EWS/exchange.asmx)
>>> message:
>>> <SOAP-ENV:Envelope
>>> xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/ty
>>>pe s" xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/me
>>>ss ages"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
>>> <SOAP-ENV:Header/>
>>> <ns1:Body>
>>> <ns2:GetFolder>
>>> <ns2:FolderShape>
>>> <ns0:BaseShape>Default</ns0:BaseShape>
>>> </ns2:FolderShape>
>>> <ns2:FolderIds>
>>> <ns0:DistinguishedFolderId Id="inbox"/>
>>> </ns2:FolderIds>
>>> </ns2:GetFolder>
>>> </ns1:Body>
>>> </SOAP-ENV:Envelope>
>>> DEBUG:suds.client:headers = {'SOAPAction':
>>> u'"http://schemas.microsoft.com/exchange/services/2006/messages/G
>>>et Folder"', 'Content-Type': 'text/xml'}
>>>
>>> Should the fact that it's UTF-8 encoded be in the headers or
>>> request somewhere like so:
>>
>> Suds probably should be setting the content-type http header as
>> described in ticket 251.
>> (https://fedorahosted.org/suds/ticket/251). Can you try and let me
>> know if this fixes your problem?
>
> Weird, I use this code:
>
> headers = {'Content-Type': 'text/xml; charset=utf-8'}
> c =
> suds.client.Client('file:///home/jkugler/crc/local-tools/services.w
>sdl', transport=ntlm,
> headers=headers)
>
> And Suds still tells me it's only sending 'text/xml' as the type.
> Leading to the same error.
>
> DEBUG:suds.client:sending to (https://myserver/ews/exchange.asmx)
> message:
> <SOAP-ENV:Envelope
> xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/type
>s" xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/mess
>ages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
> <SOAP-ENV:Header/>
> <ns1:Body>
> <ns2:GetFolder>
> <ns2:FolderShape>
> <ns0:BaseShape>Default</ns0:BaseShape>
> </ns2:FolderShape>
> <ns2:FolderIds>
> <ns0:DistinguishedFolderId Id="inbox"/>
> </ns2:FolderIds>
> </ns2:GetFolder>
> </ns1:Body>
> </SOAP-ENV:Envelope>
> DEBUG:suds.client:headers = {'SOAPAction':
> u'"http://schemas.microsoft.com/exchange/services/2006/messages/Get
>Folder"', 'Content-Type': 'text/xml'}
>
> In the failed message back from the server, it starts:
>
> <?xml version="1.0" encoding="utf-8"?>
>
> Is that what needs to be added?
Yup, this should probably be added too. Most servers don't seem to
care but ... Anyway, In r671, (0.4 beta) I added "<?xml version="1.0"
encoding="utf-8"?>" and updated the default http headers so that
content-type="text/xml; charset=utf-8" All my regression tests
against my (and public) servers pass so it seems safe to make these
changes. Hope this helps.
Thanks! That seems to get me further, but now I'm hitting another
error:
<h1>Bad Request (Invalid Verb)</h1>
which generates this traceback:
Traceback (most recent call last):
File "./get_mail.py", line 39, in <module>
{'_Id':'inbox'}})
File "build/bdist.linux-i686/egg/suds/client.py", line 539, in
__call__
File "build/bdist.linux-i686/egg/suds/client.py", line 598, in invoke
File "build/bdist.linux-i686/egg/suds/client.py", line 627, in send
File "build/bdist.linux-i686/egg/suds/client.py", line 659, in
succeeded
File "build/bdist.linux-i686/egg/suds/bindings/binding.py", line 146,
in get_reply
AttributeError: 'NoneType' object has no attribute 'promotePrefixes'
I don't have time to troubleshoot right now, but I will later, and will
post a full code samle.
j
--
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
11:54 p.m.
New subject: Server error, WAS: Re: Suds not using UTF-8 encoding?
So, here's the debug output:
DEBUG:suds.client:sending to
(https://webmail.crchealth.com/ews/exchange.asmx)
message:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/types...
xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/messa...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns1:Body>
<ns2:GetFolder>
<ns2:FolderShape>
<ns0:BaseShape>Default</ns0:BaseShape>
</ns2:FolderShape>
<ns2:FolderIds>
<ns0:DistinguishedFolderId Id="inbox"/>
</ns2:FolderIds>
</ns2:GetFolder>
</ns1:Body>
</SOAP-ENV:Envelope>
DEBUG:suds.client:headers = {'SOAPAction':
u'"http://schemas.microsoft.com/exchange/services/2006/messages/...;,
'Content-Type': 'text/xml;
charset=utf-8'}
DEBUG:suds.client:http succeeded:
<h1>Bad Request (Invalid Verb)</h1>
Traceback (most recent call last):
File "./get_mail.py", line 43, in <module>
{'_Id':'inbox'}})
File "/home/jkugler/src/suds-trunk/suds/client.py", line 539, in
__call__
return client.invoke(args, kwargs)
File "/home/jkugler/src/suds-trunk/suds/client.py", line 598, in
invoke
result = self.send(msg)
File "/home/jkugler/src/suds-trunk/suds/client.py", line 627, in send
result = self.succeeded(binding, reply.message)
File "/home/jkugler/src/suds-trunk/suds/client.py", line 659, in
succeeded
r, p = binding.get_reply(self.method, reply)
File "/home/jkugler/src/suds-trunk/suds/bindings/binding.py", line
146, in get_reply
soapenv.promotePrefixes()
AttributeError: 'NoneType' object has no attribute 'promotePrefixes'
So, the error is expected given the reply from the server.
Code snippet:
import suds
from suds.transport.https import WindowsHttpAuthenticated
logging.basicConfig(level=logging.CRITICAL)
logging.getLogger('suds.client').setLevel(logging.DEBUG)
ntlm = WindowsHttpAuthenticated(username=r'DOMAIN\user',
password='****')
c =
suds.client.Client('file:///home/jkugler/crc/local-tools/services.wsdl',
transport=ntlm,
headers=headers)
print c.service.GetFolder({'BaseShape':'Default'},
{'DistinguishedFolderId':
{'_Id':'inbox'}})
The example for this call is here:
http://msdn.microsoft.com/en-us/library/aa580274(v=EXCHG.140).aspx
Differences:
Namespace designators...but you declare them in the envelope, so that
shouldn't be an issue.
"UTF-8" is lower case in the example. *Really* shouldn't matter, but who
knows.
I also noticed that the SOAPAction in the header is double quoted: that
is: u'"...."' Is there a reason for that?
Suds does this:
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
The MS example does this:
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
I don't have enough knowledge of soap to know if any of these things
(should) matter.
The other issue I'm having that I alluded to is that the NTLM module (or
transport) seems to be having major issues with my company's server.
I'm going to have to found out if they are running 2003 or 2008. But
what happens is it just sits there and then finally generates this
traceback:
Traceback (most recent call last):
File "./get_mail.py", line 42, in <module>
{'_Id':'inbox'}})
File "/home/jkugler/src/suds-trunk/suds/client.py", line 539, in
__call__
return client.invoke(args, kwargs)
File "/home/jkugler/src/suds-trunk/suds/client.py", line 598, in
invoke
result = self.send(msg)
File "/home/jkugler/src/suds-trunk/suds/client.py", line 623, in send
reply = transport.send(request)
File "/home/jkugler/src/suds-trunk/suds/transport/https.py", line 64,
in send
return HttpTransport.send(self, request)
File "/home/jkugler/src/suds-trunk/suds/transport/http.py", line 77,
in send
fp = self.u2open(u2request)
File "/home/jkugler/src/suds-trunk/suds/transport/http.py", line 118,
in u2open
return url.open(u2request, timeout=tm)
File "/usr/lib/python2.6/urllib2.py", line 395, in open
response = meth(req, response)
File "/usr/lib/python2.6/urllib2.py", line 508, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.6/urllib2.py", line 427, in error
result = self._call_chain(*args)
File "/usr/lib/python2.6/urllib2.py", line 367, in _call_chain
result = func(*args)
File
"/usr/local/lib/python2.6/dist-packages/python_ntlm-1.0-py2.6.egg/ntlm/HTTPNtlmAuthHandler.py",
line 96, in http_error_401
return self.http_error_authentication_required('www-authenticate',
req, fp, headers)
File
"/usr/local/lib/python2.6/dist-packages/python_ntlm-1.0-py2.6.egg/ntlm/HTTPNtlmAuthHandler.py",
line 35, in http_error_authentication_required
return self.retry_using_http_NTLM_auth(req, auth_header_field, None,
headers)
File
"/usr/local/lib/python2.6/dist-packages/python_ntlm-1.0-py2.6.egg/ntlm/HTTPNtlmAuthHandler.py",
line 86, in retry_using_http_NTLM_auth
raise urllib2.URLError(err)
urllib2.URLError: <urlopen error [Errno 104] Connection reset by peer>
But, I'm not sure if that's a Suds issue.
Anyway, I'll see what I can do to get around this.
j
--
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
12:14 p.m.
New subject: python-ntlm timing out on POST (Was: Suds not using UTF-8 encoding?)
You mention python-ntlm timing out doing POSTs... I'm having just that
very problem. Did you ever come up with a solution?
On 10-04-03 2:33 AM, Joshua J. Kugler wrote:
So, in my ongoing saga getting suds working with MS Exchange 2007
(which
I'm sure you'll hear a lot more about before I'm done :) ), I hit an a
couple interesting snags.
python-ntlm seems to time out against the server when doing POST
requests (but get requests seem fine). But that's not the current
issue.
When one of my requests went through, I got back this message:
suds.WebFault: Server raised fault: 'Server was unable to process
request. ---> Input message does not conform to Simple SOAP Binding
Profile Version 1.0. Requirement R1012: A MESSAGE MUST serialize the
envelope using either UTF-8 or UTF-16 character encoding.'
I thought Suds encoded everything in UTF-8 be default. The debug output
is below:
DEBUG:suds.client:sending to (https://myserver/EWS/exchange.asmx)
message:
<SOAP-ENV:Envelope
xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/types...
xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/messa...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns1:Body>
<ns2:GetFolder>
<ns2:FolderShape>
<ns0:BaseShape>Default</ns0:BaseShape>
</ns2:FolderShape>
<ns2:FolderIds>
<ns0:DistinguishedFolderId Id="inbox"/>
</ns2:FolderIds>
</ns2:GetFolder>
</ns1:Body>
</SOAP-ENV:Envelope>
DEBUG:suds.client:headers = {'SOAPAction':
u'"http://schemas.microsoft.com/exchange/services/2006/messages/...;,
'Content-Type': 'text/xml'}
Should the fact that it's UTF-8 encoded be in the headers or request
somewhere like so:
<?xml version="1.0" encoding="UTF-8"?>
Where is the errant behavior? Me? Suds? Exchange?
j
12:21 p.m.
New subject: python-ntlm timing out on POST (Was: Suds not using UTF-8 encoding?)
On Tuesday 06 April 2010, Chris Rose elucidated thus:
You mention python-ntlm timing out doing POSTs... I'm having
just
that very problem. Did you ever come up with a solution?
I have not yet. But I'm glad to know I'm not the only one having this
problem. It is not, technically, a timeout (in the HTTP sense of the
word), but the remote side is hanging up, which might indicate that the
client (urllib2 or python-ntlm) is not behaving correctly.
That last line of my traceback is:
File
"/usr/local/lib/python2.6/dist-packages/python_ntlm-1.0-py2.6.egg/ntlm/HTTPNtlmAuthHandler.py",
line 86, in retry_using_http_NTLM_auth
raise urllib2.URLError(err)
urllib2.URLError: <urlopen error [Errno 104] Connection reset by peer>
It might be time to bring the python-ntlm author in on the conversation.
I'll try to work up a test case.
j
On 10-04-03 2:33 AM, Joshua J. Kugler wrote:
> So, in my ongoing saga getting suds working with MS Exchange 2007
> (which I'm sure you'll hear a lot more about before I'm done :) ),
> I hit an a couple interesting snags.
>
> python-ntlm seems to time out against the server when doing POST
> requests (but get requests seem fine). But that's not the current
> issue.
>
> When one of my requests went through, I got back this message:
>
> suds.WebFault: Server raised fault: 'Server was unable to process
> request. ---> Input message does not conform to Simple SOAP
> Binding Profile Version 1.0. Requirement R1012: A MESSAGE MUST
> serialize the envelope using either UTF-8 or UTF-16 character
> encoding.'
>
> I thought Suds encoded everything in UTF-8 be default. The debug
> output is below:
>
> DEBUG:suds.client:sending to (https://myserver/EWS/exchange.asmx)
> message:
> <SOAP-ENV:Envelope
> xmlns:ns0="http://schemas.microsoft.com/exchange/services/2006/type
>s" xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:ns2="http://schemas.microsoft.com/exchange/services/2006/mess
>ages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
> <SOAP-ENV:Header/>
> <ns1:Body>
> <ns2:GetFolder>
> <ns2:FolderShape>
> <ns0:BaseShape>Default</ns0:BaseShape>
> </ns2:FolderShape>
> <ns2:FolderIds>
> <ns0:DistinguishedFolderId Id="inbox"/>
> </ns2:FolderIds>
> </ns2:GetFolder>
> </ns1:Body>
> </SOAP-ENV:Envelope>
> DEBUG:suds.client:headers = {'SOAPAction':
> u'"http://schemas.microsoft.com/exchange/services/2006/messages/Get
>Folder"', 'Content-Type': 'text/xml'}
>
> Should the fact that it's UTF-8 encoded be in the headers or
> request somewhere like so:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> Where is the errant behavior? Me? Suds? Exchange?
>
> j
_______________________________________________
suds mailing list
suds(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/suds
--
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
5151
days inactive
5154
days old
7 comments
3 participants
participants (3)
-
Chris Rose -
Jeff Ortel -
Joshua J. Kugler