Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81024
| Date | 2014-11-19 14:08 +1100 |
|---|---|
| From | Cameron Simpson <cs@zip.com.au> |
| Subject | Re: Trouble getting full response content from PATCH request |
| References | <m4dll8$69d$1@reader1.panix.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.15988.1416366536.18130.python-list@python.org> (permalink) |
On 17Nov2014 20:26, John Gordon <gordon@panix.com> wrote:
>I'm working with a third-party API and I'm seeing some behavior that I
>can't explain.
>
>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 <body> 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 <html> or <body>
>tags.
[...]
You need a "SOAPAction: " HTTP header with SOAP requests. It may be that
simple.
Cheers,
Cameron Simpson <cs@zip.com.au>
Glendower: I can call monsters from the vasty deeps.
Hotspur: Why, so can I, or so can any man. But will they come when you do
call them?
- Henry IV, part 1
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Trouble getting full response content from PATCH request John Gordon <gordon@panix.com> - 2014-11-17 20:26 +0000
Re: Trouble getting full response content from PATCH request Cameron Simpson <cs@zip.com.au> - 2014-11-19 14:08 +1100
Re: Trouble getting full response content from PATCH request John Gordon <gordon@panix.com> - 2014-11-19 17:17 +0000
Re: Trouble getting full response content from PATCH request Cameron Simpson <cs@zip.com.au> - 2014-11-20 21:17 +1100
csiph-web