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! Go to Solution.
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.
After this change, it was observed that the Proxy and Target Endpoints were available in the downloaded API Proxy.
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.
After this change, it was observed that the Proxy and Target Endpoints were available in the downloaded API Proxy.
User | Count |
---|---|
7 | |
2 | |
2 | |
1 | |
1 |