-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to serve swagger over https? What are the correct settings? #227
Comments
Your issue looks similar to #132 |
I fixed this like this:
|
@cwalkatron: I just added the way I fixed this same issue to #132 |
@cwalkatron can you please show more code how you fixed it? I tried to use the ProxyFix without any success.
Even with that I still get the cross-origin issue. |
I was missing one line in my nginx.conf |
With the update of werkzeug to 0.15. The above fix may need some parameters update to work as before. We are using the ELB of AWS, so need to update the |
Absolutely do not make a broad recommendation to set every value to 1. Each value should be set based on the specific hosting setup for each application. This is relevant to security, and is described in the documentation for |
Hi, The discussions will take place in #223 since your issue is quite similar. |
I'm now closing this issue. |
Related to #132 where I found the correct Fix for Flask-Restplus with Nginx and gunicorn |
I have working swagger when accessing it over HTTP, but when I try to access it over HTTPS I get following error:
swagger-ui.min.js:10 Mixed Content: The page at 'https://www.little-hero.tk/api/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://www.little-hero.tk/api/swagger.json'. This request has been blocked; the content must be served over HTTPS.
Full printscreen: http://i.imgur.com/jms8bdh.png
What should I do? There is no information in docs. I'm using cloudflare to get https if it helps.
The text was updated successfully, but these errors were encountered: