-
Notifications
You must be signed in to change notification settings - Fork 87
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
HTTPS Configuration for Apache Server and Swagger #598
Comments
Please add configuration for the Snowstorm Nginx location to inform Snowstorm which host and protocol the proxy is running on.
Then Swagger should display the correct protocol. |
That's not possible in this case since I just built it from docker-compose file and I'm not managing the proxy. |
The only way that I know of to make Swagger aware of the protocol that it's using is to set the X-Forwarded-Proto header. This is a standard HTTP header that is intended for this purpose when using a proxy. |
Tried with that header in Apache and still didn't work. May be there is something that you can do in the code? |
Hi @leapoli , The Spring Boot We set the
This causes Swagger to realise that it's hosted on https. This Swagger UI is here: https://browser.ihtsdotools.org/snowstorm/snomed-ct/ The quickest way to test this is that the "servers" section of the generated swagger json has "https". My understanding is that all swagger UI calls use this server URL. https://browser.ihtsdotools.org/snowstorm/snomed-ct/v3/api-docs/snowstorm If we remove the I'm sure this must be possible with Apache server but I am struggling to find an authoritative and up to date guide on how to set it up. |
Thank you @kaicode for reopening this case. I still cannot figure out what could be happening, taking into cosideration that Apache proxy is forwarding this header to the Snowstorm server (and there isn't in the middle). I will research also trying to arrive at a solution. |
Hi
I'm facing an issue when using Snowstorm 10.2.1, since it's generating an URL but without considering the protocol, so the browser is blocking request due mixed content (HTTP and HTTPS).
The server is hosted at: https://snowstorm.entrerios.gov.ar/ so that the generated URL is:
I'm not sure if this is an issue or something that I'd configure. I've deployed it with docker and there is a browser redirecting from HTTP to HTTPS, but the thing here is that the browser is avoiding request formed this way.
The text was updated successfully, but these errors were encountered: