Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Generator3 needs SSL. OAS3.0 Client Generation Broken
See original GitHub issueQ&A (please complete the following information)
- OS: Ubuntu 18.04
- Browser: Chrome
- Version: 66.0.3359.181
- Method of installation: n/a
- Swagger-Editor version: whatver is currently at editor.swagger.io
- Swagger/OpenAPI version: OpenAPI 3.0
Example Swagger/OpenAPI definition: https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore.yaml
Describe the bug you’re encountering
I just want to generate HTML client code for my OpenAPI 3.0 yaml. When I try it with the OAS3.0 petstore example (see above), it throws a mixed content error:
index.js:1 Mixed Content: The page at 'https://editor.swagger.io/' was loaded over HTTPS, but requested an insecure resource 'http://generator3.swagger.io/api/generator.json'. This request has been blocked; the content must be served over HTTPS.
To reproduce…
Steps to reproduce the behavior:
- Go to editor.swagger.io
- Paste in the OAS3.0 petstore code from https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore.yaml
- Click generate client code in HTML
- See error
Expected behavior
HTML client gets downloaded for OAS3.0 stuff
Screenshots
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@delmartechdude no problem! Glad to hear it.
We run releases weekly, so you should see this fixed on Swagger.io around this time of day on Friday.
In the meantime, using the Editor over HTTP should let you work around the issue!
@shockey Yeah…I mean I assume my definition is valid because I’m not getting errors or rendering problems in Swagger Editor. So I’ve opened an issue with the Codegen people (https://github.com/swagger-api/swagger-codegen/issues/8222)