SwaggerUI comes with an explicit NOTICE fileĬontaining additional legal notices and information. SwaggerUI is licensed under Apache 2.0 license. Please disclose any security-related issues or vulnerabilities by emailing instead of using the public issue tracker.
Swagger editor cors support update#
This list will update regularly, and will not include features that were not implemented in previous versions. Consider to book our support service and help. To help with the migration, here are the currently known issues with 3.X. The Swagger Editor sends requests directly from browser which leads to CORS error and work with it is not. Swagger UI works in the latest versions of Chrome, Safari, Firefox, and Edge. Integration tests can be run locally with npm run e2e - be sure you aren't running a dev server when testing! Browser support You will need JDK of version 7 or higher as instructed here Compatibility between Swagger UI and the OpenAPI Specification is as follows: Swagger UI Version The OpenAPI Specification has undergone 5 revisions since initial creation in 2010.
Swagger editor cors support download#
If you are looking for plain ol' HTML/JS/CSS, download the latest release and copy the contents of the /dist folder to your server. We strongly suggest that you use swagger-ui instead of swagger-ui-dist if you're building a single-page application, since swagger-ui-dist is significantly larger.
This library returnsĤ00 Bad Request for requests that don't conform to the specĤ03 Forbidden for invalid origins or headers.Ģ) Return CORS headers in the response and let the browser sort out the access details. This is the route taken by the Java CORS filter project.
I did some research into this and it seems like behavior falls into two camps:ġ) Return an error if the CORS request is invalid. Yes, I realize I'm answering my own question, but here it goes anyway.