Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Data Action - Error 403 when switching to new server

  • 1.  Data Action - Error 403 when switching to new server

    Posted 06-05-2025 18:40

    Greg_Walters | 2018-09-14 15:03:25 UTC | #1

    We're moving a web service to a new server, going from IIS 7 to IIS 10.

    We have set up the new server as close to the old server as possible. The existing data action has been running with Purecloud for over a year.

    When we try to run a data action test on the new server we get: { "status": 400, "code": "bad.request", "message": "The request could not be understood by the server due to malformed syntax.", "messageParams": {}, "contextId": "366715b4-521b-494c-9455-f1168469cc5f", "details": [], "errors": [ { "status": 403, "code": "BAD_REQUEST", "message": "Target referenced forbidden private IP space", "messageParams": {}, "details": [], "errors": [] } ] }

    The Configuration Request for the new call: { "requestUrlTemplate": "https://agenttest.*.org/NetForumMessageQueueWebService/api/ConstituentGiftDetails?actkey=${input.actkey}&cstkey=${input.cst_key}", "requestType": "GET", "headers": { "Transfer-Encoding": "buffered" }, "requestTemplate": "${input.rawRequest}" }

    The Configuration Request for the existing call: { "requestUrlTemplate": "https://agent.*.org/NetForumMessageQueueWebService/api/ConstituentGiftDetails?actkey=${input.actkey}&cstkey=${input.cstkey}", "requestType": "GET", "headers": { "Transfer-Encoding": "buffered" }, "requestTemplate": "${input.rawRequest}" }

    The rest of the Contracts and Configurations are identical. I have gone through the forums and looked at the related posts, but not found anything that helps.

    Any ideas?

    ChrisDibble | 2018-09-14 17:42:51 UTC | #2

    Hi Greg,

    The error is being caused by the underscore in the hostname agent_test. As part of running an action, we verify that actions do not attempt to interact with local IP addresses. The underscore in your hostname is causing a false positive on that safety check because technically a hostname containing a _ is not considered valid. Renaming your endpoint to something like agentTest or agent-test should resolve the issue.

    For more information on hostnames, see https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names and the referenced RFCs

    -Chris

    Greg_Walters | 2018-09-14 19:49:18 UTC | #3

    That worked!

    Thanks Chris!!

    system | 2018-10-15 19:49:21 UTC | #4

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 3555



Related Content