Response body has "no content" in Swagger UI

[Andrew McFarland Campbell]

Hi,

I'm having problems with Swagger UI

My Swagger UI is at http://127.0.0.1/~acam0006/swagger-ui/dist/, and my .yaml is at http://127.0.0.1/~acam0006/login.yaml

Swagger UI loads the yaml without any problems when I enter the URI into the URI field and click "Explore".

There is one end point in my .yaml. When I click "Try it out", I get the following results:

Response Body

no content

Response Code

0

Response Headers

{
  "error": "no response from server"
}

The curl works on the command line, and the request URI is correct.

Can anyone help me fix this?

[tony tam]

Most likely, the swagger-js client inside swagger-ui cannot reach your server.  Perhaps a CORS issue?

If you can open the debug tab in your browser and share any errors, that’d be helpful.

--
You received this message because you are subscribed to the Google Groups "Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew McFarland Campbell]

From the javascript console:

swagger-ui.js:1715 server doesn't consume application/x-www-form-urlencoded, try ["application/json"]

(index):1 XMLHttpRequest cannot load http://internal.url/path/to/resource. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1' is therefore not allowed access.

2swagger-ui.js:1715 server doesn't consume application/x-www-form-urlencoded, try ["application/json"]

Where "http://internal.url/path/to/resource" is the URI for the resource.

[tony tam]

Looks like you need to enable CORS then.  Do you have the ability to return 200 for OPTIONS requests?  Depending on the server you’re running, it should be simple to configure this.

[Andrew McFarland Campbell]

Thanks. I don't control the server, but I'll speak to the team that does.

[Ron Ratovsky]

If you don’t control the server but still want to get this to work, you can use a CORS proxy, at least for initial testing.

--

[Andrew McFarland Campbell]

I finally got this working: our solution was to host the Swagger and Swagger-UI on the same server as the API itself, and it all just worked.

Thanks for all the help!