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