​Have you tried setting the verify depth to 2? That way you hit the
intermediate and root CA certs in the chain.
On Fri, 05/05/2017 01.58, Doug Maurer wrote:
>
We have a setup where we have to use MIL CAC's to access our site. It
> currently works with SSLVerifyClient require and SSLVerifyDepth
As far as I know, unless you are acting as a man-in-the middle type caching
where you are decrypting and re-encrypting the https on the proxy, you
cannot cache httsp. The https is an encrypted stream so there is no way to
cache the object as apache cannot see them.
Robert
On Sun, 28 Aug 2016
So in your case, the "*" means all interfaces and all IP's.
So you would be able to hit https on eth0 with IP 10.10.10.1 and on eth1
with IP 172.20.54.10.
On Tue, 21 Jun 2016 18:45:15 + (UTC)
Mahmood N wrote:
tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN 28122/xinetd> Shows the port, 5666, the
Not sure what you are actually looking for.
You stated, "There are some network commands (netstat -pat), but they show
the TCP port in use." Last I checked, Apache only used TCP ports. So the
netstat command that you referenced should show exactly what you need.
Here is an example from a Red H
Chris,
By your somments, I am guessing that you have a proxy in front of the http
server? Or are you just doing an inbound NAT?
Robert
On Mon, 22 Feb 2016 12:30:45 -0500
ch...@adamstelecom.com wrote:
Quick update:
Upon being onsite with my server, the HTTPS works internally using the
serv
