I did not yet see a 201 error and therefore I assume it would be fine not to send an escape message for it. From my understanding there should be no
escape message for all http status codes below 400. Thomas.
Von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]
Im Auftrag von 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:
IMPORTANT NOTICE: This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. |
-- _______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxx http://scottklement.com/mailman/listinfo/ftpapi