t;
>
>
> Are there any interim gateway devices?
>
>
>
> If so – do they manage SSL offloading?
>
>
>
> Theo
>
>
>
> *From:* Phil Smith [mailto:philbo...@gmail.com]
> *Sent:* 13 July 2016 21:47
> *To:* users@httpd.apache.org
> *Subject:* [users@httpd
No. SSLProtocol is configured properly for each VirtualHost section
including the default.
On Wed, Jul 13, 2016 at 4:48 PM, Eric Covener wrote:
> On Wed, Jul 13, 2016 at 4:46 PM, Phil Smith wrote:
> > Either setting seems to work in disabling TLSv1 if the apache server is
> >
I'm running Apache distributed via CentOS6:
Server: Apache/2.2.15 (CentOS)
I'm attempting to disable TLSv1.0 in ssl.conf using either of:
SSLProtocol all -SSLv2 -SSLv3 -TLSv1
or
SSLProtocol +TLSv1.1 +TLSv1.2
Either setting seems to work in disabling TLSv1 if the apache server is
requested via pr
This discussion is related to the bolded recommendation at:
http://httpd.apache.org/docs/2.2/mod/core.html#limit
stating that:
"In the general case, access control directives should not be placed
within a section." and further that... "A
section should always be used in preference to a section w
On Mon, Feb 11, 2013 at 10:05 PM, Igor Cicimov wrote:
>
> On 12/02/2013 1:50 PM, "Phil Smith" wrote:
>>
>> I'm trying to find some Apache documentation verifying that the access
>> configs listed below in the manner I find them to be working are truly
&g
I'm trying to find some Apache documentation verifying that the access
configs listed below in the manner I find them to be working are truly
supported by Apache and are reasonable.(I'm using Apache 2.2.3).
In a given directory in web space I have an .htaccess file with
information such as the fol
I noticed that when I placed an .htaccess file outside of web space,
the .htaccess file was respected by Apache. I found this surprising.
Say DocumentRoot is /home/joe/public_html so that /home/joe is in a
path leading to web space, but outside of web space.
An .htaccess file:
/home/joe/.htaccess
On Mon, Feb 20, 2012 at 8:54 AM, Tom Evans wrote:
> On Mon, Feb 20, 2012 at 1:16 PM, Steve Swift wrote:
>> Ah, but the "sh" error means that my code never starts executing. If the
>> very first line of my code were to get executed, then the error message
>> would come from the error handlers in m
On Sat, Feb 18, 2012 at 7:10 AM, Eric Covener wrote:
> On Sat, Feb 18, 2012 at 12:00 AM, Phil Smith wrote:
>> I'm running Apache/2.2.3 (CentOS) which is the latest version
>> available for CentOS5.
>> I'm noticing the following in my error logs:
>> sh: -c:
I'm running Apache/2.2.3 (CentOS) which is the latest version
available for CentOS5.
I'm noticing the following in my error logs:
sh: -c: line 0: unexpected EOF while looking for matching `"'
sh: -c: line 1: syntax error: unexpected end of file
They usually arrive in groups of 2-10 such messages;
10 matches
Mail list logo