service configuration files that needs to be saved just incase the server got lost someday by the cloud provider.
Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.

147 lines
7.0KB

  1. <IfModule mod_ssl.c>
  2. <VirtualHost _default_:443>
  3. ServerName draw.lawipac.com
  4. ServerAdmin sp@lawipac.com
  5. ProxyPass / http://s-gate.lawipac.com:38080/
  6. ProxyPassReverse / http://s-gate.lawipac.com:38080/
  7. # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
  8. # error, crit, alert, emerg.
  9. # It is also possible to configure the loglevel for particular
  10. # modules, e.g.
  11. #LogLevel info ssl:warn
  12. ErrorLog ${APACHE_LOG_DIR}/draw.lawipac.com.error.log
  13. CustomLog ${APACHE_LOG_DIR}/draw.lawipac.com.access.log combined
  14. # For most configuration files from conf-available/, which are
  15. # enabled or disabled at a global level, it is possible to
  16. # include a line for only one particular virtual host. For example the
  17. # following line enables the CGI configuration for this host only
  18. # after it has been globally disabled with "a2disconf".
  19. #Include conf-available/serve-cgi-bin.conf
  20. # SSL Engine Switch:
  21. # Enable/Disable SSL for this virtual host.
  22. SSLEngine on
  23. # A self-signed (snakeoil) certificate can be created by installing
  24. # the ssl-cert package. See
  25. # /usr/share/doc/apache2/README.Debian.gz for more info.
  26. # If both key and certificate are stored in the same file, only the
  27. # SSLCertificateFile directive is needed.
  28. #SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
  29. #SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
  30. #SSLCertificateFile /etc/apache2/myssl_certs/lawipac.com.crt
  31. #SSLCertificateKeyFile /etc/apache2/myssl_certs/lawipac.com.key
  32. Include /etc/letsencrypt/options-ssl-apache.conf
  33. # Server Certificate Chain:
  34. # Point SSLCertificateChainFile at a file containing the
  35. # concatenation of PEM encoded CA certificates which form the
  36. # certificate chain for the server certificate. Alternatively
  37. # the referenced file can be the same as SSLCertificateFile
  38. # when the CA certificates are directly appended to the server
  39. # certificate for convinience.
  40. #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
  41. #SSLCertificateChainFile /etc/apache2/myssl_certs/startcom_sub.class1.server.ca.pem
  42. #SSLCertificateChainFile /etc/apache2/myssl_certs/startcom_1_root_boundle.crt
  43. # Certificate Authority (CA):
  44. # Set the CA certificate verification path where to find CA
  45. # certificates for client authentication or alternatively one
  46. # huge file containing all of them (file must be PEM encoded)
  47. # Note: Inside SSLCACertificatePath you need hash symlinks
  48. # to point to the certificate files. Use the provided
  49. # Makefile to update the hash symlinks after changes.
  50. #SSLCACertificatePath /etc/ssl/certs/
  51. #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
  52. # Certificate Revocation Lists (CRL):
  53. # Set the CA revocation path where to find CA CRLs for client
  54. # authentication or alternatively one huge file containing all
  55. # of them (file must be PEM encoded)
  56. # Note: Inside SSLCARevocationPath you need hash symlinks
  57. # to point to the certificate files. Use the provided
  58. # Makefile to update the hash symlinks after changes.
  59. #SSLCARevocationPath /etc/apache2/ssl.crl/
  60. #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
  61. # Client Authentication (Type):
  62. # Client certificate verification type and depth. Types are
  63. # none, optional, require and optional_no_ca. Depth is a
  64. # number which specifies how deeply to verify the certificate
  65. # issuer chain before deciding the certificate is not valid.
  66. #SSLVerifyClient require
  67. #SSLVerifyDepth 10
  68. # SSL Engine Options:
  69. # Set various options for the SSL engine.
  70. # o FakeBasicAuth:
  71. # Translate the client X.509 into a Basic Authorisation. This means that
  72. # the standard Auth/DBMAuth methods can be used for access control. The
  73. # user name is the `one line' version of the client's X.509 certificate.
  74. # Note that no password is obtained from the user. Every entry in the user
  75. # file needs this password: `xxj31ZMTZzkVA'.
  76. # o ExportCertData:
  77. # This exports two additional environment variables: SSL_CLIENT_CERT and
  78. # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
  79. # server (always existing) and the client (only existing when client
  80. # authentication is used). This can be used to import the certificates
  81. # into CGI scripts.
  82. # o StdEnvVars:
  83. # This exports the standard SSL/TLS related `SSL_*' environment variables.
  84. # Per default this exportation is switched off for performance reasons,
  85. # because the extraction step is an expensive operation and is usually
  86. # useless for serving static content. So one usually enables the
  87. # exportation for CGI and SSI requests only.
  88. # o OptRenegotiate:
  89. # This enables optimized SSL connection renegotiation handling when SSL
  90. # directives are used in per-directory context.
  91. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
  92. <FilesMatch "\.(cgi|shtml|phtml|php)$">
  93. SSLOptions +StdEnvVars
  94. </FilesMatch>
  95. <Directory /usr/lib/cgi-bin>
  96. SSLOptions +StdEnvVars
  97. </Directory>
  98. # SSL Protocol Adjustments:
  99. # The safe and default but still SSL/TLS standard compliant shutdown
  100. # approach is that mod_ssl sends the close notify alert but doesn't wait for
  101. # the close notify alert from client. When you need a different shutdown
  102. # approach you can use one of the following variables:
  103. # o ssl-unclean-shutdown:
  104. # This forces an unclean shutdown when the connection is closed, i.e. no
  105. # SSL close notify alert is send or allowed to received. This violates
  106. # the SSL/TLS standard but is needed for some brain-dead browsers. Use
  107. # this when you receive I/O errors because of the standard approach where
  108. # mod_ssl sends the close notify alert.
  109. # o ssl-accurate-shutdown:
  110. # This forces an accurate shutdown when the connection is closed, i.e. a
  111. # SSL close notify alert is send and mod_ssl waits for the close notify
  112. # alert of the client. This is 100% SSL/TLS standard compliant, but in
  113. # practice often causes hanging connections with brain-dead browsers. Use
  114. # this only for browsers where you know that their SSL implementation
  115. # works correctly.
  116. # Notice: Most problems of broken clients are also related to the HTTP
  117. # keep-alive facility, so you usually additionally want to disable
  118. # keep-alive for those clients, too. Use variable "nokeepalive" for this.
  119. # Similarly, one has to force some clients to use HTTP/1.0 to workaround
  120. # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
  121. # "force-response-1.0" for this.
  122. BrowserMatch "MSIE [2-6]" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
  123. # MSIE 7 and newer should be able to use keepalive
  124. BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
  125. Include /etc/letsencrypt/options-ssl-apache.conf
  126. SSLCertificateFile /etc/letsencrypt/live/lawipac.com/fullchain.pem
  127. SSLCertificateKeyFile /etc/letsencrypt/live/lawipac.com/privkey.pem
  128. Include /etc/letsencrypt/options-ssl-apache.conf
  129. </VirtualHost>
  130. </IfModule>
  131. # vim: syntax=apache ts=4 sw=4 sts=4 sr noet