Re: [Ftpapi] Payload Limitation

Scott,

Thanks for the reply.

In fact, I had already changed my service to use the HTTP_REQ instead of HTTPSTRING(), the reason I mentioned it in the subject.

Still, the result is the same after the software update.

The wrapper function I use to call HTTP_REQ

The place it gets the length, it returns 100000 always....and this is the issue i guess.

Returns 400 -"Bad request error" as the payload is cut off

Thanks,

Robin

On Thu, Jan 14, 2021 at 4:33 PM Scott Klement <sk@xxxxxxxxxxxxxxxx> wrote:

Robin,

There was a bug in an old version of HTTPAPI that prevented HTTP_req()
(i.e. the routine you mention in your subject line) from working with
more than 100k worth of data. Updating your HTTPAPI was to resolve
this problem.

It won't change HTTP_string(), which is a different routine. There are
no plans to change HTTP_string(). HTTP_string() is meant for simple,
more quick-n-dirty applications. 99% of the people using HTTPAPI don't
need to work with strings larger than 100K. If you do, you can simply
use HTTP_req().

--
Scott Klement
sk@xxxxxxxxxxxxxxxx

On 1/13/2021 12:57 PM, Robin Jacob wrote:
>
> I read through the community support and found the limitation on
> HTTP_STRING() is now resolved with latest version.
>
> Is installing new HTTPAPI version is the only option now to overcome
> this 100K limitation?
>
>
--
_______________________________________________
Ftpapi mailing list
Ftpapi@xxxxxxxxxxxxxxxxxxxxxx
http://scottklement.com/mailman/listinfo/ftpapi

Re: [Ftpapi] Payload Limitation - Using HTTP_REQ()