That won't work. You must define it in the global scope. If you have several ssl vhosts and only set SSLProtocol in the vhost context, the value from the first vhost would take precedence.
On Wed, Jul 13, 2016 at 4:53 PM, Phil Smith <philbo...@gmail.com> wrote: > No. SSLProtocol is configured properly for each VirtualHost section > including the default. > > On Wed, Jul 13, 2016 at 4:48 PM, Eric Covener <cove...@gmail.com> wrote: > >> On Wed, Jul 13, 2016 at 4:46 PM, Phil Smith <philbo...@gmail.com> wrote: >> > Either setting seems to work in disabling TLSv1 if the apache server is >> > requested via private IP address. >> > >> > However, neither seem to work in disabling TLSv1 if the apache server is >> > requested via public IP address. >> >> >> Maybe you have SSL enabled in two scopes (global, virtualhost) but >> only SSLProtocol in one of them? >> >> >> -- >> Eric Covener >> cove...@gmail.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >> >> >
