I am using Ajax Toolkit function sforce.connection.remoteFunction. What are the limitations of this method? For example if I send an encoded Blob content as a request, is there any limitation on the size of the request I send?


I've never managed to hit the limits on this function, and not for a lack of trying. I've written scripts on my personal server that returned payloads in the hundreds of megabytes, and the proxy worked just fine. I've also posted hundreds of megabytes of data in a single call.

As far as I know, there's no documentation on what limits exist, other than the fact that hosts must be on certain ports (80, 443, or 1024-65535), and that port 80 and 443 only allow insecure and secure connections (respectively), and hosts must be pre-configured by administrators to allow access. Of course, doing things that break the normal rules of HTTP may not be supported, such as using an unknown HTTP verb.

  • Thats a good news @sfdcfox. I need to send a huge binary data to external systems. Do you think that would be a concern? – NoNicknameSFDC Oct 21 '16 at 9:55
  • 1
    @NoNicknameSFDC From what I recall, you should be able to send and receive payloads of pretty much any size. Of course, I'd set up a quick test and confirm this, as it's been a while since I've last experimented with this, but you shouldn't have any problems from what I remember. – sfdcfox Oct 21 '16 at 14:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.