comparison Sphinx/source/faq/https.rst @ 17:114506f51e70

https
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 21 Jun 2016 08:57:03 +0200
parents 901e8961f46e
children 669ea65ba7fb
comparison
equal deleted inserted replaced
16:b12e2c1d9fed 17:114506f51e70
7 It is highly desirable to enable HTTPS (SSL) encryption with Orthanc 7 It is highly desirable to enable HTTPS (SSL) encryption with Orthanc
8 to protect its REST API, as it provides access to medical 8 to protect its REST API, as it provides access to medical
9 information. To this end, you have two possibilites: 9 information. To this end, you have two possibilites:
10 10
11 1. Put Orthanc behind an enterprise-ready HTTPS server such as 11 1. Put Orthanc behind an enterprise-ready HTTPS server such as
12 :ref:`Apache <apache>` or :ref:`nginx <nginx>`. 12 :ref:`Apache <apache>`, :ref:`nginx <nginx>` or :ref:`Microsoft IIS <iis>`.
13 2. For simple deployments, use Orthanc :ref:`built-in HTTPS server <https-builtin>`. 13 2. For simple deployments, use Orthanc :ref:`built-in HTTPS server <https-builtin>`.
14 14
15 **You should always favor the first option**. The second option might make 15 **You should always favor the first option**. The second option might make
16 sense in the context of an hospital Intranet, i.e. the Orthanc server 16 sense in the context of an hospital Intranet, i.e. the Orthanc server
17 is not publicly accessible from the Internet. 17 is not publicly accessible from the Internet.