Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!gordon From: John Gordon Newsgroups: comp.lang.python Subject: Re: Trouble getting full response content from PATCH request Date: Wed, 19 Nov 2014 17:17:08 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 26 Message-ID: References: NNTP-Posting-Host: panix1.panix.com X-Trace: reader1.panix.com 1416417428 21207 166.84.1.1 (19 Nov 2014 17:17:08 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Wed, 19 Nov 2014 17:17:08 +0000 (UTC) User-Agent: nn/6.7.3 Xref: csiph.com comp.lang.python:81035 In Cameron Simpson writes: > >The API uses the HTTP PATCH operation to set user passwords, and in > >case of unacceptable passwords, the response is supposed to be an HTML > >document containing a diagnostic message in the tag. > > > >When I submit my test data via a functional testing tool (SoapUI), it > >behaves as expected. > > > >However, when I submit test data from Python code, the response content > >consists only of the diagnostic message, with no enclosing or > >tags. > [...] > You need a "SOAPAction: " HTTP header with SOAP requests. It may be that > simple. The API does provide some SOAP calls, but the specific call I'm using is REST. Is there a corresponding header I should use? Thanks. -- John Gordon Imagine what it must be like for a real medical doctor to gordon@panix.com watch 'House', or a real serial killer to watch 'Dexter'.