Importing an API proxy results in missing proxy and target endpoints

When importing a downloaded API proxy version definition, the proxy and target endpoints are missing. However, in another API Proxy, we don't observe this issue.

Here are the steps that we followed:


Failing Scenario:
1) Exported revision 2 of Public-Proxy_rev2
2) Created a new API Proxy TestProxy3-Public.
3) Upload new revision -> Public-Proxy_rev2.


We notice that the proxy and target endpoints are missing.

Success Scenario:
1) Exported revision 4 of Private-Proxy_rev4.
2) Created a new API Proxy TestProxy3-Private.
3) Upload new revision -> Private-Proxy_rev5.

For some reason, we notice that this works. That is, the proxy and target endpoints exist in this case.

Can you please check why does it fail in the case of Public_Proxy_rev2 ?

Solved Solved
0 1 128
1 ACCEPTED SOLUTION

  1. I had a look at both the API Proxies Public-Proxy (revision 2) and Private-Proxy (revision 4).
  2. I noticed one big difference between the two API Proxies is that the Proxy and Target Endpoints have special characters "{" and "}" in Public-Proxy (revision 2).
    • For example, here's one of the Proxy Endpoint having special characters -> V{VersionNumber}-Proxy-Endpoint
  3. However, these special characters were not there in Private-Proxy (revision 4).
  4. As per the documentation of Proxy Endpoint , the name of the ProxyEndpoint should follow the below rules:

    Must be unique within the API proxy configuration, when (in rare cases) multiple ProxyEndpoints are defined. The characters you are allowed to use in the name are restricted to the following: A-Z0-9._\-$ %.

Same rules hold good for Target Endpoints as well.

  • The reason for missing Proxy and Target Endpoints in the downloaded API Proxy Public-Proxy was that they had the special characters "{" and "}", which are not allowed in the Proxy and Target Endpoint name.
  • Solution:
    1. Remove the special characters "{" and "}" from the Proxy and Target Endpoints. Ensure the names are adhering to rules provided in the above documentation.
    2. Save the changes as new revision.
    3. Download the new revision.

    After this change, it was observed that the Proxy and Target Endpoints were available in the downloaded API Proxy.

    View solution in original post

    1 REPLY 1

    1. I had a look at both the API Proxies Public-Proxy (revision 2) and Private-Proxy (revision 4).
    2. I noticed one big difference between the two API Proxies is that the Proxy and Target Endpoints have special characters "{" and "}" in Public-Proxy (revision 2).
      • For example, here's one of the Proxy Endpoint having special characters -> V{VersionNumber}-Proxy-Endpoint
    3. However, these special characters were not there in Private-Proxy (revision 4).
    4. As per the documentation of Proxy Endpoint , the name of the ProxyEndpoint should follow the below rules:

      Must be unique within the API proxy configuration, when (in rare cases) multiple ProxyEndpoints are defined. The characters you are allowed to use in the name are restricted to the following: A-Z0-9._\-$ %.

    Same rules hold good for Target Endpoints as well.

  • The reason for missing Proxy and Target Endpoints in the downloaded API Proxy Public-Proxy was that they had the special characters "{" and "}", which are not allowed in the Proxy and Target Endpoint name.
  • Solution:
    1. Remove the special characters "{" and "}" from the Proxy and Target Endpoints. Ensure the names are adhering to rules provided in the above documentation.
    2. Save the changes as new revision.
    3. Download the new revision.

    After this change, it was observed that the Proxy and Target Endpoints were available in the downloaded API Proxy.