OpenAPI Import - Bad Request

[#1]

Was trying Use OpenAPI option in Apigee to upload swagger documentation, but seems it is not accepting any Valid url.

I am able to get the proper json when I try it from browser...

.

[anilsr]

@Sam Maniscalco , Are you using Apigee Edge OPDK ? If Yes, Can you make sure the URL is accessible from the machines where Apigee Edge is running ?

[#3]

HI Anil,

yes we are using OPDK and I am able to access/download the file directly to the server

curl -v -o topology.yaml https://trail-notes-uat.cfappsawsnpeast-hto.ebiz.verizon.com/v2/api-docs?group=topology-api
% Total  % Received % Xferd  Average Speed  Time  Time  Time  Current Dload  Upload  Total  Spent  Left  Speed
0  0  0  0  0  0  0  0 --:--:-- --:--:-- --:--:--  0
* About to connect() to trail-notes-uat.cfappsawsnpeast-hto.ebiz.verizon.com port 443 (#0)
* Connected to trail-notes-uat.cfappsawsnpeast-hto.ebiz.verizon.com port 443 (#0)
100  4594  0  4594  0  0  7102  0 --:--:-- --:--:-- --:--:--  7100
* Connection #0 to host trail-notes-uat.cfappsawsnpeast-hto.ebiz.verizon.com left intact

[#4]

Hi Sam,

Please use developer tools on chrome browser to pinpoint the error when you hit the apply button. The network group will help indicate the messages being sent and the response that management api is getting.

Please share what you find.

[#5 · Accepted solution]

OPDK needs a special property set in ui.properties

https://docs.apigee.com/private-cloud/latest/allowing-trace-tool-access-local-ip-addresses

conf_apigee-base_apigee.feature.enabletraceforinternaladdresses="true"
conf_apigee-base_apigee.feature.enableopenapiforinternaladdresses="true"
conf_apigee-base_apigee.feature.enablewsdlforinternaladdresses="true"