Update HTTP & HTTPS Callout Endpoint: Any action needed?

  • Resolved waytogo

    (@waytogo)


    8 years, 3 months ago

    Salesforce emailed my client in June 2016 with the following message. Do I need to worry about this in regard to your plugin? I assume probably not since it’s after July 9 and plugin works. Thank you.

    We will be retiring IP addresses targeted in HTTP and HTTPS callouts for the NA5, NA17, NA18, NA19, NA20, NA22, NA23, NA41, CS21, CS22, CS23, CS24, CS25, CS26, CS27, and CS28 instances on July 7, 2016.

    As an admin of a Salesforce org that has made an HTTP or HTTPS callout in the last month, you may need to take action to avoid impact to your organization.

    What action do I need to take?
    If your org makes HTTP or HTTPS callouts to endpoints that permit only 96.43.147.8 or 96.43.151.8 as source IP addresses, you will need to update those endpoints’ source IP trust lists to cover the entire collection of Salesforce IP ranges documented in the What are the Salesforce IP Addresses & Domains to whitelist article. If you do not update these source IP trust lists, callouts from your org may begin to fail starting July 7, 2016, impacting your service experience.

    If you are following Salesforce’s best practices and have added the entire collection of Salesforce IP ranges to HTTP and HTTPS callout endpoints’ source IP address trust lists, you do not need to take any action. In addition, no action is required for HTTP or HTTPS callout endpoints that do not restrict by source IP address.

    https://www.ads-software.com/plugins/salesforce-wordpress-to-lead/

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Update HTTP & HTTPS Callout Endpoint: Any action needed?’ is closed to new replies.