-
Notifications
You must be signed in to change notification settings - Fork 270
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
Serving the Swagger UI over HTTPS fails #193
Comments
hey! this was likely introduced due to #173 . i will have a look later today. |
@lysnikolaou can you confirm that this works for you? pretty sure it should. would do a minor release afterwards |
Hey @tfranzel, thanks for the quick response! Unfortunately, |
thanks for checking it out so quickly. i'm a bit puzzled here. i made all rendered urls relative so no http/s mixing should be going on for swagger ui. are you certain your install has the most-recent master?
to be sure but |
Yup, it must have been some wrong configuration on my part. Upgrading to 0.11.1 fixes this. Thanks a bunch for the quick fix. |
Hey hey,
thanks for the awesome work you've been doing 🚀. We have encountered an error, that we think is related to how
drf-spectacular
serves the schema as HTML.Describe the bug
Trying to access the Swagger UI on our staging system, which can only be accessed through HTTPS, fails with
Expected behavior
We'd expect that we could deploy our docs and serve it over HTTPS without problems.
The text was updated successfully, but these errors were encountered: