Skip to content

Instantly share code, notes, and snippets.

@adojos

adojos/apache_multiPort_multiHost_httpd-ssl.conf.md

Last active August 11, 2024 19:36
Show Gist options
  • Save adojos/f556f3a5e25a472297f1448f48d3f64a to your computer and use it in GitHub Desktop.
Save adojos/f556f3a5e25a472297f1448f48d3f64a to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. adojos revised this gist Oct 5, 2022. 1 changed file with 23 additions and 9 deletions.
    32 changes: 23 additions & 9 deletions apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -7,7 +7,7 @@ In order to have a multi-port configuration for different virtual hosts (project

    **1. httpd.conf** (\XAMPP\apache\conf\)

    **2. httpd-ssl.conf** (\XAMPP\apache\conf\extra\) :point_down: _This file_ :point_down:
    **2. httpd-ssl.conf** (\XAMPP\apache\conf\extra\)

    **3. httpd-vhosts.conf** (\XAMPP\apache\conf\extra\)

    @@ -24,29 +24,43 @@ In order to have a multi-port configuration for different virtual hosts (project
    </br>
    Checkout the following gist links for complete changes to above configuration files each:
    Checkout following gist links for complete changes to Apache to achieve above target scenario:
    <sup>
    [1. [Part 1 of 4] Apache Multi-Port & Multi-Host 'httpd.conf' Config](https://gist.github.com/adojos/e1c103ec974f2eeca3028d1daff1b377)
    [2. [Part 2 of 4] Apache Multi-Port & Multi-Host 'httpd-ssl.conf' Config](https://gist.github.com/adojos/f556f3a5e25a472297f1448f48d3f64a)
    [3. [Part 3 of 4] Apache Multi-Port & Multi-Host 'httpd-vhosts.conf'](https://gist.github.com/adojos/9507e8ab36b636e04a31f37a02c9766e)
    [4. [Part 4 of 4] Apache Multi-Port & Multi-Host Windows hosts file Config](https://gist.github.com/adojos/d95cb097f7c9d6feb5098adc7d26387c)
    </sup>
    </br>
    ### httpd-ssl.conf (\XAMPP\apache\conf\extra\)
    ### Config Changes for httpd-ssl.conf (\XAMPP\apache\conf\extra\) :point_down: _This file_ :point_down:
    Note the changes done for following directives in this file:
    We need to change the following directives in this file:
    ```
    (a) HTTPS Listen Port
    (b) HTTPS ServerName
    (c) VirtualHost Directive for httpd-ssl
    ```
    #### Step 1
    As per our above stated ***'target scenario'***, we would add _'4 HTTPS Listen Ports'_ as shown below _(Also make sure that default port is 80 is commented out by sign '#', as not needed):_
    ```
    \#Listen 443
    Listen 8082
    Listen 8084
    Listen 8086
    Listen 8088
    ```
    #### Step 2
    Secondly, we modify the value of the 'HTTPS ServerName' directive as below (again make sure that default directive is commented out by sign '#'):
    \#ServerName localhost:80
    ServerName localhost:8081
    </br>
    **:point_right: NOTE:** _Do not copy the whole file 'as-is', because it has been lifted from my production environment and may have hard-coded directory paths. I recommend only to refer the quoted key changes/modifications_
  2. adojos revised this gist Sep 30, 2022. 1 changed file with 4 additions and 4 deletions.
    8 changes: 4 additions & 4 deletions apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -26,13 +26,13 @@ In order to have a multi-port configuration for different virtual hosts (project
    Checkout the following gist links for complete changes to above configuration files each:
    [1. Config for 'httpd.conf' to Implement multiple ports and multiple-virtualHosts [Part 1 of 4]](https://gist.github.com/adojos/e1c103ec974f2eeca3028d1daff1b377)
    [1. [Part 1 of 4] Apache Multi-Port & Multi-Host 'httpd.conf' Config](https://gist.github.com/adojos/e1c103ec974f2eeca3028d1daff1b377)
    [2. Config for 'httpd-ssl.conf' to Implement multiple ports and multiple-virtualHosts [Part 2 of 4]](https://gist.github.com/adojos/f556f3a5e25a472297f1448f48d3f64a)
    [2. [Part 2 of 4] Apache Multi-Port & Multi-Host 'httpd-ssl.conf' Config](https://gist.github.com/adojos/f556f3a5e25a472297f1448f48d3f64a)
    [3. Config for 'httpd-vhosts.conf' to Implement multiple ports and multiple-virtualHosts [Part 3 of 4]](https://gist.github.com/adojos/9507e8ab36b636e04a31f37a02c9766e)
    [3. [Part 3 of 4] Apache Multi-Port & Multi-Host 'httpd-vhosts.conf'](https://gist.github.com/adojos/9507e8ab36b636e04a31f37a02c9766e)
    [4. Config for 'windows 'hosts' file' to Implement multiple ports and multiple-virtualHosts [Part 4 of 4]](https://gist.github.com/adojos/d95cb097f7c9d6feb5098adc7d26387c)
    [4. [Part 4 of 4] Apache Multi-Port & Multi-Host Windows hosts file Config](https://gist.github.com/adojos/d95cb097f7c9d6feb5098adc7d26387c)
    </br>
  3. adojos revised this gist Sep 30, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    ## Apache 'httpd-ssl.conf' Config for Multi-Port & Multi-Host [Part 2 of 4]
    ## [Part 2 of 4] Apache Multi-Port & Multi-Host 'httpd-ssl.conf' Config

    </br>
    In order to have a multi-port configuration for different virtual hosts (projects, websites) on Apache in XAMPP, you need to make changes to the following 3 Apache configuration files and 1 windows host file:
  4. adojos revised this gist Sep 30, 2022. 1 changed file with 9 additions and 4 deletions.
    13 changes: 9 additions & 4 deletions apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    ## Configuring Apache for Multi-Port & Multi-Host via httpd-ssl.conf
    ## Apache 'httpd-ssl.conf' Config for Multi-Port & Multi-Host [Part 2 of 4]

    </br>
    In order to have a multi-port configuration for different virtual hosts (projects, websites) on Apache in XAMPP, you need to make changes to the following 3 Apache configuration files and 1 windows host file:
    @@ -26,9 +26,14 @@ In order to have a multi-port configuration for different virtual hosts (project
    Checkout the following gist links for complete changes to above configuration files each:
    1. XAMPP | Apache: Config for 'httpd.conf' to Implement multiple ports and multiple-virtualHosts [Part 1 of 4]
    2. XAMPP | Apache: Config for 'httpd-ssl.conf' to Implement multiple ports and multiple-virtualHosts [Part 2 of 4]
    3. XAMPP | Apache: Config for 'httpd-vhosts.conf' to Implement multiple ports and multiple-virtualHosts [Part 3 of 4]
    [1. Config for 'httpd.conf' to Implement multiple ports and multiple-virtualHosts [Part 1 of 4]](https://gist.github.com/adojos/e1c103ec974f2eeca3028d1daff1b377)
    [2. Config for 'httpd-ssl.conf' to Implement multiple ports and multiple-virtualHosts [Part 2 of 4]](https://gist.github.com/adojos/f556f3a5e25a472297f1448f48d3f64a)
    [3. Config for 'httpd-vhosts.conf' to Implement multiple ports and multiple-virtualHosts [Part 3 of 4]](https://gist.github.com/adojos/9507e8ab36b636e04a31f37a02c9766e)
    [4. Config for 'windows 'hosts' file' to Implement multiple ports and multiple-virtualHosts [Part 4 of 4]](https://gist.github.com/adojos/d95cb097f7c9d6feb5098adc7d26387c)
    </br>
  5. adojos revised this gist Sep 29, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -32,7 +32,7 @@ Checkout the following gist links for complete changes to above configuration fi
    </br>
    ### httpd-ssl.conf (\XAMPP\apache\conf)
    ### httpd-ssl.conf (\XAMPP\apache\conf\extra\)
    Note the changes done for following directives in this file:
  6. adojos revised this gist Sep 29, 2022. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -28,6 +28,7 @@ Checkout the following gist links for complete changes to above configuration fi
    1. XAMPP | Apache: Config for 'httpd.conf' to Implement multiple ports and multiple-virtualHosts [Part 1 of 4]
    2. XAMPP | Apache: Config for 'httpd-ssl.conf' to Implement multiple ports and multiple-virtualHosts [Part 2 of 4]
    3. XAMPP | Apache: Config for 'httpd-vhosts.conf' to Implement multiple ports and multiple-virtualHosts [Part 3 of 4]
    </br>
  7. adojos revised this gist Sep 29, 2022. 1 changed file with 4 additions and 0 deletions.
    4 changes: 4 additions & 0 deletions apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -43,6 +43,10 @@ Note the changes done for following directives in this file:
    </br>
    **:point_right: NOTE:** _Do not copy the whole file 'as-is', because it has been lifted from my production environment and may have hard-coded directory paths. I recommend only to refer the quoted key changes/modifications_
    </br>
    ```shell
    #
    # This is the Apache server configuration file providing SSL support.
  8. adojos created this gist Sep 29, 2022.
    347 changes: 347 additions & 0 deletions apache_multiPort_multiHost_httpd-ssl.conf.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,347 @@
    ## Configuring Apache for Multi-Port & Multi-Host via httpd-ssl.conf

    </br>
    In order to have a multi-port configuration for different virtual hosts (projects, websites) on Apache in XAMPP, you need to make changes to the following 3 Apache configuration files and 1 windows host file:
    </br>
    </br>

    **1. httpd.conf** (\XAMPP\apache\conf\)

    **2. httpd-ssl.conf** (\XAMPP\apache\conf\extra\) :point_down: _This file_ :point_down:

    **3. httpd-vhosts.conf** (\XAMPP\apache\conf\extra\)

    **4. Windows 'hosts' file** (C:\Windows\System32\drivers\etc)

    </br>

    #### :point_right: Target Scenario:
    > ``` Making the above changes to your configuration files, you achieve the following target scenario -
    > 1) Implement 4 named and independent Virtual Hosts
    > 2) Implement 4 different HTTP ports for above Virtual Hosts (8081, 8083, 8085, 8087)
    > 3) Implement 4 different HTTPS ports for above Virtual Hosts (8082, 8084, 8086, 8088)
    > ```
    </br>
    Checkout the following gist links for complete changes to above configuration files each:
    1. XAMPP | Apache: Config for 'httpd.conf' to Implement multiple ports and multiple-virtualHosts [Part 1 of 4]
    2. XAMPP | Apache: Config for 'httpd-ssl.conf' to Implement multiple ports and multiple-virtualHosts [Part 2 of 4]
    </br>
    ### httpd-ssl.conf (\XAMPP\apache\conf)
    Note the changes done for following directives in this file:
    ```
    (a) HTTPS Listen Port
    (b) HTTPS ServerName
    (c) VirtualHost Directive for httpd-ssl
    ```
    </br>
    ```shell
    #
    # This is the Apache server configuration file providing SSL support.
    # It contains the configuration directives to instruct the server how to
    # serve pages over an https connection. For detailed information about these
    # directives see <URL:http://httpd.apache.org/docs/2.4/mod/mod_ssl.html>
    #
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    #
    # Required modules: mod_log_config, mod_setenvif, mod_ssl,
    # socache_shmcb_module (for default value of SSLSessionCache)
    #
    # Pseudo Random Number Generator (PRNG):
    # Configure one or more sources to seed the PRNG of the SSL library.
    # The seed data should be of good random quality.
    # WARNING! On some platforms /dev/random blocks if not enough entropy
    # is available. This means you then cannot use the /dev/random device
    # because it would lead to very long connection times (as long as
    # it requires to make more entropy available). But usually those
    # platforms additionally provide a /dev/urandom device which doesn't
    # block. So, if available, use this one instead. Read the mod_ssl User
    # Manual for more details.
    #
    #SSLRandomSeed startup file:/dev/random 512
    #SSLRandomSeed startup file:/dev/urandom 512
    #SSLRandomSeed connect file:/dev/random 512
    #SSLRandomSeed connect file:/dev/urandom 512
    #
    # When we also provide SSL we have to listen to the
    # standard HTTP port (see above) and to the HTTPS port
    #
    # Listen 443
    Listen 8082
    Listen 8084
    Listen 8086
    Listen 8088
    ##
    ## SSL Global Context
    ##
    ## All SSL configuration in this context applies both to
    ## the main server and all SSL-enabled virtual hosts.
    ##
    # SSL Cipher Suite:
    # List the ciphers that the client is permitted to negotiate,
    # and that httpd will negotiate as the client of a proxied server.
    # See the OpenSSL documentation for a complete list of ciphers, and
    # ensure these follow appropriate best practices for this deployment.
    # httpd 2.2.30, 2.4.13 and later force-disable aNULL, eNULL and EXP ciphers,
    # while OpenSSL disabled these by default in 0.9.8zf/1.0.0r/1.0.1m/1.0.2a.
    SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
    SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
    # By the end of 2016, only TLSv1.2 ciphers should remain in use.
    # Older ciphers should be disallowed as soon as possible, while the
    # kRSA ciphers do not offer forward secrecy. These changes inhibit
    # older clients (such as IE6 SP2 or IE8 on Windows XP, or other legacy
    # non-browser tooling) from successfully connecting.
    #
    # To restrict mod_ssl to use only TLSv1.2 ciphers, and disable
    # those protocols which do not support forward secrecy, replace
    # the SSLCipherSuite and SSLProxyCipherSuite directives above with
    # the following two directives, as soon as practical.
    # SSLCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA
    # SSLProxyCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA
    # User agents such as web browsers are not configured for the user's
    # own preference of either security or performance, therefore this
    # must be the prerogative of the web server administrator who manages
    # cpu load versus confidentiality, so enforce the server's cipher order.
    SSLHonorCipherOrder on
    # SSL Protocol support:
    # List the protocol versions which clients are allowed to connect with.
    # Disable SSLv3 by default (cf. RFC 7525 3.1.1). TLSv1 (1.0) should be
    # disabled as quickly as practical. By the end of 2016, only the TLSv1.2
    # protocol or later should remain in use.
    SSLProtocol all -SSLv3
    SSLProxyProtocol all -SSLv3
    # Pass Phrase Dialog:
    # Configure the pass phrase gathering process.
    # The filtering dialog program (`builtin' is an internal
    # terminal dialog) has to provide the pass phrase on stdout.
    SSLPassPhraseDialog builtin
    # Inter-Process Session Cache:
    # Configure the SSL Session Cache: First the mechanism
    # to use and second the expiring timeout (in seconds).
    #SSLSessionCache "shmcb:D:/DEV-WORKSPACE/XAMPP/apache/logs/ssl_scache(512000)"
    SSLSessionCache "shmcb:D:/DEV-WORKSPACE/XAMPP/apache/logs/ssl_scache(512000)"
    SSLSessionCacheTimeout 300
    # OCSP Stapling (requires OpenSSL 0.9.8h or later)
    #
    # This feature is disabled by default and requires at least
    # the two directives SSLUseStapling and SSLStaplingCache.
    # Refer to the documentation on OCSP Stapling in the SSL/TLS
    # How-To for more information.
    #
    # Enable stapling for all SSL-enabled servers:
    #SSLUseStapling On
    # Define a relatively small cache for OCSP Stapling using
    # the same mechanism that is used for the SSL session cache
    # above. If stapling is used with more than a few certificates,
    # the size may need to be increased. (AH01929 will be logged.)
    #SSLStaplingCache "shmcb:${SRVROOT}/logs/ssl_stapling(32768)"
    # Seconds before valid OCSP responses are expired from the cache
    #SSLStaplingStandardCacheTimeout 3600
    # Seconds before invalid OCSP responses are expired from the cache
    #SSLStaplingErrorCacheTimeout 600
    ##
    ## SSL Virtual Host Context
    ##
    # <VirtualHost _default_:443>
    <VirtualHost _default_:8082>
    # General setup for the virtual host
    DocumentRoot "D:/DEV-WORKSPACE/XAMPP/htdocs"
    # ServerName www.example.com:8082
    ServerName localhost:8082
    ServerAdmin [email protected]
    ErrorLog "D:/DEV-WORKSPACE/XAMPP/apache/logs/error.log"
    TransferLog "D:/DEV-WORKSPACE/XAMPP/apache/logs/access.log"
    # SSL Engine Switch:
    # Enable/Disable SSL for this virtual host.
    SSLEngine on
    # Server Certificate:
    # Point SSLCertificateFile "conf/ssl.crt/server.crt"
    # the certificate is encrypted, then you will be prompted for a
    # pass phrase. Note that a kill -HUP will prompt again. Keep
    # in mind that if you have both an RSA and a DSA certificate you
    # can configure both in parallel (to also allow the use of DSA
    # ciphers, etc.)
    # Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)
    # require an ECC certificate which can also be configured in
    # parallel.
    SSLCertificateFile "conf/ssl.crt/server.crt"
    #SSLCertificateFile "conf/ssl.crt/server.crt"
    #SSLCertificateFile "conf/ssl.crt/server.crt"
    # Server Private Key:
    # If the key is not combined with the certificate, use this
    # directive to point at the key file. Keep in mind that if
    # you've both a RSA and a DSA private key you can configure
    # both in parallel (to also allow the use of DSA ciphers, etc.)
    # ECC keys, when in use, can also be configured in parallel
    SSLCertificateKeyFile "conf/ssl.key/server.key"
    #SSLCertificateKeyFile "conf/ssl.key/server.key"
    #SSLCertificateKeyFile "conf/ssl.key/server.key"
    # Server Certificate Chain:
    # Point SSLCertificateChainFile at a file containing the
    # concatenation of PEM encoded CA certificates which form the
    # certificate chain for the server certificate. Alternatively
    # the referenced file can be the same as SSLCertificateFile "conf/ssl.crt/server.crt"
    # certificate for convenience.
    #SSLCertificateChainFile "${SRVROOT}/conf/server-ca.crt"
    # Certificate Authority (CA):
    # Set the CA certificate verification path where to find CA
    # certificates for client authentication or alternatively one
    # huge file containing all of them (file must be PEM encoded)
    # Note: Inside SSLCACertificatePath you need hash symlinks
    # to point to the certificate files. Use the provided
    # Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath "${SRVROOT}/conf/ssl.crt"
    #SSLCACertificateFile "${SRVROOT}/conf/ssl.crt/ca-bundle.crt"
    # Certificate Revocation Lists (CRL):
    # Set the CA revocation path where to find CA CRLs for client
    # authentication or alternatively one huge file containing all
    # of them (file must be PEM encoded).
    # The CRL checking mode needs to be configured explicitly
    # through SSLCARevocationCheck (defaults to "none" otherwise).
    # Note: Inside SSLCARevocationPath you need hash symlinks
    # to point to the certificate files. Use the provided
    # Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath "${SRVROOT}/conf/ssl.crl"
    #SSLCARevocationFile "${SRVROOT}/conf/ssl.crl/ca-bundle.crl"
    #SSLCARevocationCheck chain
    # Client Authentication (Type):
    # Client certificate verification type and depth. Types are
    # none, optional, require and optional_no_ca. Depth is a
    # number which specifies how deeply to verify the certificate
    # issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth 10
    # TLS-SRP mutual authentication:
    # Enable TLS-SRP and set the path to the OpenSSL SRP verifier
    # file (containing login information for SRP user accounts).
    # Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for
    # detailed instructions on creating this file. Example:
    # "openssl srp -srpvfile ${SRVROOT}/conf/passwd.srpv -add username"
    #SSLSRPVerifierFile "${SRVROOT}/conf/passwd.srpv"
    # Access Control:
    # With SSLRequire you can do per-directory access control based
    # on arbitrary complex boolean expressions containing server
    # variable checks and other lookup directives. The syntax is a
    # mixture between C and Perl. See the mod_ssl documentation
    # for more details.
    #<Location />
    #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
    # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
    # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
    #</Location>
    # SSL Engine Options:
    # Set various options for the SSL engine.
    # o FakeBasicAuth:
    # Translate the client X.509 into a Basic Authorisation. This means that
    # the standard Auth/DBMAuth methods can be used for access control. The
    # user name is the `one line' version of the client's X.509 certificate.
    # Note that no password is obtained from the user. Every entry in the user
    # file needs this password: `xxj31ZMTZzkVA'.
    # o ExportCertData:
    # This exports two additional environment variables: SSL_CLIENT_CERT and
    # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    # server (always existing) and the client (only existing when client
    # authentication is used). This can be used to import the certificates
    # into CGI scripts.
    # o StdEnvVars:
    # This exports the standard SSL/TLS related `SSL_*' environment variables.
    # Per default this exportation is switched off for performance reasons,
    # because the extraction step is an expensive operation and is usually
    # useless for serving static content. So one usually enables the
    # exportation for CGI and SSI requests only.
    # o StrictRequire:
    # This denies access when "SSLRequireSSL" or "SSLRequire" applied even
    # under a "Satisfy any" situation, i.e. when it applies access is denied
    # and no other module can change it.
    # o OptRenegotiate:
    # This enables optimized SSL connection renegotiation handling when SSL
    # directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
    SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory "D:/DEV-WORKSPACE/XAMPP/apache/cgi-bin">
    SSLOptions +StdEnvVars
    </Directory>
    # SSL Protocol Adjustments:
    # The safe and default but still SSL/TLS standard compliant shutdown
    # approach is that mod_ssl sends the close notify alert but doesn't wait for
    # the close notify alert from client. When you need a different shutdown
    # approach you can use one of the following variables:
    # o ssl-unclean-shutdown:
    # This forces an unclean shutdown when the connection is closed, i.e. no
    # SSL close notify alert is sent or allowed to be received. This violates
    # the SSL/TLS standard but is needed for some brain-dead browsers. Use
    # this when you receive I/O errors because of the standard approach where
    # mod_ssl sends the close notify alert.
    # o ssl-accurate-shutdown:
    # This forces an accurate shutdown when the connection is closed, i.e. a
    # SSL close notify alert is send and mod_ssl waits for the close notify
    # alert of the client. This is 100% SSL/TLS standard compliant, but in
    # practice often causes hanging connections with brain-dead browsers. Use
    # this only for browsers where you know that their SSL implementation
    # works correctly.
    # Notice: Most problems of broken clients are also related to the HTTP
    # keep-alive facility, so you usually additionally want to disable
    # keep-alive for those clients, too. Use variable "nokeepalive" for this.
    # Similarly, one has to force some clients to use HTTP/1.0 to workaround
    # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    # "force-response-1.0" for this.
    BrowserMatch "MSIE [2-5]" \
    nokeepalive ssl-unclean-shutdown \
    downgrade-1.0 force-response-1.0
    # Per-Server Logging:
    # The home of a custom SSL log file. Use this when you want a
    # compact non-error SSL logfile on a virtual host basis.
    CustomLog "D:/DEV-WORKSPACE/XAMPP/apache/logs/ssl_request.log" \
    "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
    </VirtualHost>
    ```