Try opening up the browser console and sharing the error message that you get.
> On Nov 18, 2016, at 6:29 AM, Jasmine <feng.jasmin...@gmail.com> wrote: > > More info: I am using Swagger 2.0. I tested out the format of the JSON in the > Swagger Editor and it displayed correctly, however the same JSON caused a > CORS error with Swagger UI, so I believe it is not a format issue. I know > swagger doesn't support web sockets, but I just want to use the nice display. > Thanks! > > On Friday, November 18, 2016 at 9:25:12 AM UTC-5, Jasmine wrote: > I would like to use swagger UI for documenting my websockets. However, I get > a "Can't read from server. It may not have the appropriate > access-control-origin settings." error when loading. I used the same format > in my JSON as I did for my rest api, which worked fine. If I don't care about > the testing and connection features, how do I only use the UI component and > avoid a cors error? > > -- > 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-swaggersocket+unsubscr...@googlegroups.com > <mailto:swagger-swaggersocket+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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-swaggersocket+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
