Search found 3 matches
- Mon Apr 11, 2022 7:22 pm
- Forum: HTTPAPI
- Topic: Capturing HTTP 400/500 responses
- Replies: 4
- Views: 8322
Re: Capturing HTTP 400/500 responses
Resolved by just defining exactly as in the definition, I'll move it to response from there.
- Mon Apr 11, 2022 5:59 pm
- Forum: HTTPAPI
- Topic: Capturing HTTP 400/500 responses
- Replies: 4
- Views: 8322
Re: Capturing HTTP 400/500 responses
Scott,
Thanks for the quick response. Originally went http_req because that's what we have used in the past, but was getting a RNF7535 - and since I couldn't solve that I changed to the http_string (and that compiled.)
Details on RNF7535:
*RNF7535 30 031200 The type and attributes of parameter 4 ...
Thanks for the quick response. Originally went http_req because that's what we have used in the past, but was getting a RNF7535 - and since I couldn't solve that I changed to the http_string (and that compiled.)
Details on RNF7535:
*RNF7535 30 031200 The type and attributes of parameter 4 ...
- Mon Apr 11, 2022 4:07 pm
- Forum: HTTPAPI
- Topic: Capturing HTTP 400/500 responses
- Replies: 4
- Views: 8322
Capturing HTTP 400/500 responses
I'm doing a POST operation to consume an API, and capturing the response:
response = http_string('POST':URL:json:'application/json');
I also have a monitor on there for an error.
Everything works great with an HTTP 200 response. I get the response as I'm expecting it.
But if the API fails ...
response = http_string('POST':URL:json:'application/json');
I also have a monitor on there for an error.
Everything works great with an HTTP 200 response. I get the response as I'm expecting it.
But if the API fails ...