| Just to follow up as promised.
The assurances were not true. The log showed that the full payload was being sent.
What it also hinted at (and we subsequently verified) was that the underlying design of the Web Service had been changed without telling anybody!
And I don't just mean a small change - a BIG one. The service now sends 3nn, 4nn, and 5nn messages whereas all the documentation says 200s for everything except incorrect URL basically.
The service provider had sent an updated yml file - but with no hint that it was anything other than a minor change - not a a major redesign ...
So http_string is no longer appropriate and we have to change the interface logic.
Sigh ....
My first thought - but I am assured that is not the case. We will see when I session with them tomorrow.
Are you sure he isn't looking at it in debug and seeing only the first 1024 characters by default in the debug eval command? I get that all the time from my GETURI customers on both the sending and returning data. I'll be conducting a debug session with the tomorrow. Will let you know.
> On Jul 1, 2020, at 3:51 PM, Scott Klement <sk@xxxxxxxxxxxxxxxx> wrote:
>
> I'm not aware of any such limitation. Show me how to reproduce it, please.
>
> On 7/1/2020 2:21 PM, Jon Paris wrote:
>> I have a client using http_string who claims it is sending only 1,024 bytes to the web service. The proto says it is good for 1Mb.
>>
>> I seem to recall reading before that one of the HTTP API methods only handle up to 1,024 but I can't find the reference so it may just be my ancient memory.
>>
>>
> --
> _______________________________________________
> Ftpapi mailing list
> Ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> http://scottklement.com/mailman/listinfo/ftpapi
--
_______________________________________________
Ftpapi mailing list
Ftpapi@xxxxxxxxxxxxxxxxxxxxxx
http://scottklement.com/mailman/listinfo/ftpapi
-- _______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxxhttp://scottklement.com/mailman/listinfo/ftpapi
|