Dave
I know you're trying the curl approach now, but did you ever try
logging the request/response in the original post command?
From earlier mail:
Dave
As you are getting back data (even if truncated), I'm guessing that
Rev (libUrl) isn't seeing any error. But just to confirm, are you
checking "the result" after each post? The normal "result" for this
kind of problem is "socket closed before end of file".
It might be useful to check that it isn't a basic problem on the
server side such as setting a wrong Content-length header. You could
do this by either using libUrlSetLogField to log all requests/
responses, or if you can detect programmatically when a problem has
occurred, use libUrlLastRHHeaders() to get the response from the
server. (You'd need to do this before the next post command)
As a start, it would let us know whether the server is using Content-
length, or chunked transfer encoding, or neither. (It sounds like
neither)
To answer your very original question, there is no limit imposed on
the amount of data returned by a post command.
Cheers
Dave
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
