Hi Scott, Ah, that makes sense. I agree that http_string and http_strmf should not send an escape message. 201 is a typical response code returned from our web services when we are doing a post. We also receive this response
when we call a third party web service. Thank you so much for your response! Marina From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx <ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx>
On Behalf Of Scott Klement Hi Marina, The reason HTTPAPI returns an "error" on response code 201 is because 201 means something different from 200. 200 is the "normal" response meaning that everything was received correctly, but 201 means that a resource was created before returning successfully.
HTTPAPI wants to make that clear so that your application can make the distinction between 200 and 201 in case it matters to you. Perhaps http_string/http_stmf should not send an escape message in that case, though? That would probably be more intuitive. I think I'll change that. Would this change cause any problems for anyone reading this list? -SK On 5/24/18 1:15 PM, Marina Schwenk wrote:
|
-- _______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxx http://scottklement.com/mailman/listinfo/ftpapi