Activity › Forums › Salesforce® Discussions › Why SOAP services are not cacheable in Salesforce?

Tagged: , , , , , , , , ,

  • Avnish

    Member
    August 8, 2018 at 12:28 pm

    Hi Madhulika,

    SOAP services are not cacheable in Salesforce because SOAP when using HTTP as the transfer mechanism is sent via HTTP POST requests. As HTTP POST is non-idempotent, it is not cached at the HTTP level.

    Thanks.

  • shariq

    Member
    September 17, 2018 at 11:24 pm

    Hi,

    To add more -

    REST does not prescribe any particular mechanism for how to encode request parameters in the URL. What is recommended is that clients never do any URL synthesis: let the server do all the URL creation (by whatever mechanism you want, such as embedding within the path or as query parameters). What you definitely shouldn't do is have a GET where the client sends a body to the server! Any cache is likely to lose that. Instead, when that request doesn't correspond to a simple fetch of some resource, you POST or PUT that complex document to the server and GET the result of the operation as a separate stage.

    Hope it helps.

Log In to reply.

Popular Salesforce Blogs

Popular Salesforce Videos

Report

Harassment or bullying behavior
Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Mobile App Reported Contents
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .