You should block access in php file.
For example:
You define using defined ( 'ACCESS'... in any file you want direct access
and put the line below to every php files:
defined ( 'ACCESS' ) or die ( 'Restricted Access' );
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,264663,264694#msg-
I use this modules for compiling nginx for streaming videos on my web site
by these options :
nginx version: nginx/1.8.1
built by gcc 4.9.2 (Debian 4.9.2-10)
built with OpenSSL 1.0.1k 8 Jan 2015
TLS SNI support enabled
configure arguments: --sbin-path=/usr/sbin/nginx
--conf-path=/etc/nginx/nginx.
On Sun, Feb 21, 2016 at 11:23:02AM +0200, Thierry wrote:
Hi there,
> After I have executed the curl command, it seems that I have an answer
> from my Apache2 back end server (apache2.conf)
> Yes I do see the "Public-Key-Pins:" line... And yes I do have the
> content that I expect.
That's g
Dear sir,
After I have executed the curl command, it seems that I have an answer
from my Apache2 back end server (apache2.conf)
Yes I do see the "Public-Key-Pins:" line... And yes I do have the
content that I expect.
Public-Key-Pins:
pin-sha256="DZNsRcNIolhfdouihfazormhrfozef=";pin-sha256=
On Sun, Feb 21, 2016 at 10:22:31AM +0200, Thierry wrote:
Hi there,
> Thx for your help, but I still do have the same problem.
>
> Public Key Pinning (HPKP) No
>
> I don't know what to do anymore ...
curl -I https://your-server/your-test-url
Every line in that response comes from your ng
Dear Andreas,
Thx for your help, but I still do have the same problem.
Public Key Pinning (HPKP) No
I don't know what to do anymore ...
Thierry
Le samedi 20 février 2016 à 13:10:16, vous écriviez :
> Thierry:
>> Nginx: front end - reverse proxy
>> Apache2: Back end - web server
> h
