<VirtualHost *:443>
    ServerAdmin webmaster@test.local
    DocumentRoot X:/var/www/vhosts/test/httpdocs/
    
	ServerName test.local
    
	#LogLevel debug
	
	ErrorLog X:/var/www/vhosts/test/logs/error.log
    CustomLog X:/var/www/vhosts/test/logs/access.log combined

	#PassEnv TEMP
	#PassEnv TMP
		
	RewriteLog X:/var/www/vhosts/test/logs/mod_rewrite.log
	RewriteLogLevel 2
	
	
	#   SSL Engine Switch:
	#   Enable/Disable SSL for this virtual host.
	SSLEngine on

	#   SSL Protocol support:
	#   List the protocol versions which clients are allowed to
	#   connect with. Disable SSLv2 by default (cf. RFC 6176).
	SSLProtocol all -SSLv2

	#   SSL Cipher Suite:
	#   List the ciphers that the client is permitted to negotiate.
	#   See the mod_ssl documentation for a complete list.
	SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5

	#   Speed-optimized SSL Cipher configuration:
	#   If speed is your main concern (on busy HTTPS servers e.g.),
	#   you might want to force clients to specific, performance
	#   optimized ciphers. In this case, prepend those ciphers
	#   to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
	#   Caveat: by giving precedence to RC4-SHA and AES128-SHA
	#   (as in the example below), most connections will no longer
	#   have perfect forward secrecy - if the server's key is
	#   compromised, captures of past or future traffic must be
	#   considered compromised, too.
	#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
	#SSLHonorCipherOrder on 
	 
	#   Server Certificate:
	#   Point SSLCertificateFile at a PEM encoded certificate.  If
	#   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.)
	SSLCertificateFile "X:/usr/local/apache2/ssl/server.crt"
	#SSLCertificateFile "X:/usr/local/apache2/conf/server-dsa.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.)
	SSLCertificateKeyFile "X:/usr/local/apache2/ssl/server.key"
	#SSLCertificateKeyFile "X:/usr/local/apache2/conf/server-dsa.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
	#   when the CA certificates are directly appended to the server
	#   certificate for convenience.
	#SSLCertificateChainFile "X:/usr/local/apache2/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 "X:/usr/local/apache2/conf/ssl.crt"
	#SSLCACertificateFile "X:/usr/local/apache2/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)
	#   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 "X:/usr/local/apache2/conf/ssl.crl"
	#SSLCARevocationFile "X:/usr/local/apache2/conf/ssl.crl/ca-bundle.crl"

	#   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

	#   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 "X:/var/www/vhosts/test/httpdocs/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 "X:/var/www/vhosts/test/logs/ssl_request.log" \
			  "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
		  
	<Directory X:/var/www/vhosts/test/httpdocs/>
		DirectoryIndex index.shtml index.html 
		
		Options +Includes +Indexes
		AllowOverride All
		
		AddType text/html .shtml .html
		AddOutputFilter INCLUDES .shtml .html
		XBitHack on
		
		<FilesMatch "\.(p(m|lx?)|cgi)$">
			Options +ExecCGI +FollowSymlinks
			SetHandler cgi-script
		</FilesMatch>
		
		RewriteEngine On
		
		Allow from all
	</Directory>
	
	Alias /cgi-bin/ X:/var/www/vhosts/test/httpdocs/cgi-bin/
	<Directory X:/var/www/vhosts/test/httpdocs/cgi-bin/>
		
		DirectoryIndex index.html index.pl index.cgi
		<FilesMatch "\.(p(m|lx?)|cgi)$">
			Options +ExecCGI +FollowSymlinks
			SetHandler cgi-script
		</FilesMatch>
		Options +Indexes
	</Directory>
	
	<IfModule mod_perl>
	Alias /perl/ X:/var/www/vhosts/test/httpdocs/perl/
	<Directory X:/var/www/vhosts/test/httpdocs/perl/>
		<FilesMatch "\.plx">
			Options +ExecCGI +FollowSymlinks
			SetHandler perl-script
		</FilesMatch>
	</Directory>
	</IfModule>
	
	<IfModule fcgid_module>
	Alias /fcgi-bin/ X:/var/www/vhosts/test/httpdocs/fcgi-bin/
	<Directory X:/var/www/vhosts/test/httpdocs/fcgi-bin/>
		<FilesMatch "\.f?(cgi|pl)">
			SetHandler fcgid-script
			Options +ExecCGI +FollowSymlinks
			DirectoryIndex index.fpl index.fcgi
		</FilesMatch>
	</Directory>
	</IfModule>
	
	<IfModule mod_expires.c>
		ExpiresActive On
		ExpiresDefault 				"access plus 1 weeks"

		ExpiresByType text/html			"access plus 2 hours"
		ExpiresByType application/xhtml+xml	"access plus 2 hours"

		ExpiresByType text/xml			"modification plus 1 days"
		ExpiresByType application/xml 		"modification plus 1 days"
		ExpiresByType application/rss+xml  	"modification plus 1 days"

		ExpiresByType video/quicktime 		"access plus 1 months"
		ExpiresByType audio/mpeg			"access plus 1 months"

		ExpiresByType application/pdf 		"access plus 1 weeks"
		ExpiresByType application/ps 		"access plus 1 weeks"
	</IfModule>

</VirtualHost>