Tag Info

Hot answers tagged

2

You can do the directory change by editing the Apache config file to specify a new directory and then signalling Apache to reload it's configuration (e.g. apachectl graceful or SIGHUP etc). This won't disrupt existing transactions. You can then clean up the old directories after allowing enough time for existing connections to be closed by the client ends.


1

The following configuration is (or used to be) the best configuration according to SSLLabs: SSLProtocol +TLSv1.2 +TLSv1.1 +TLSv1 SSLCompression off SSLHonorCipherOrder on SSLCipherSuite ...


1

SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-SSLv3:-EXP:!kEDH ^^^^^^^^ Disabling SSLv3 cipher suites disables all cipher suites introduced with SSL3.0. Since these ciphers suites are also used with later SSL versions (TLS1.0+) and new cipher suites were mostly introduced with TLS1.2 ...


1

I know this is an old question, but it doesn't look like it was ever answered, so for posterity's sake the answer is that 'setcap' needs to be applied to the Java binary. setcap 'cap_net_bind_service=+ep' /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/java That appears to have done the trick for me, and my ApacheDS is now running on the standard service ports. ...


1

To set apache to serve http on port 80 AND https on port 443 you have to create 2 virtual hosts: <VirtualHost *:80> ServerName your-domain.com DocumentRoot /var/www/ </VirtualHost> <VirtualHost *:443> DocumentRoot /var/www/ ServerName your-domain.com SSLEngine On SSLCertificateFile /path/to/server.crt ...


1

I have myself never had issues with Apache listening on any IPv6 address, but this is what the apache docs say: On some platforms, such as Linux and Tru64, the only way to handle both IPv6 and IPv4 is to use mapped addresses. If you want Apache to handle IPv4 and IPv6 connections with a minimum of sockets, which requires using IPv4-mapped IPv6 addresses, ...



Only top voted, non community-wiki answers of a minimum length are eligible