Hi all,
I wanted to implement certificate pinning on an upstream SSL connection of a
reverse proxy but I am struggling with the setup.
Please let me know where I am going wrong or if the expected setup should work.
My setup is as follows:
Multiple local applications ---HTTP via localhost ---> A
Apache 2.4
I have 2 virtual hosts .conf files. Each has a port 80 and port 443 section.
The config files are identical in every way except for the DocumentRoot.
Both use ProxyPassMatch for PHP-FPM
In vhost1 I can go to http://.../ index.html and index.php successfully. If I
use SSL I can go to
On 02.12.2015 23:05, Nick Kew wrote:
On Wed, 2 Dec 2015 22:11:20 +0100
Klaus Darilion wrote:
[ ...]
A puzzle indeed.
Although the DB returns the same password-hash as always, and the
browser sends the correct credentials (as in the working scenario),
Apache replies with 401.
Klaus,
You
On 02.12.2015 23:05, Nick Kew wrote:
> On Wed, 2 Dec 2015 22:11:20 +0100
> Klaus Darilion wrote:
>
>> [ ...]
>
> A puzzle indeed.
>
>> Although the DB returns the same password-hash as always, and the
>> browser sends the correct credentials (as in the working scenario),
>> Apache replies wit
On Wed, 2 Dec 2015 22:11:20 +0100
Klaus Darilion wrote:
> [ ...]
A puzzle indeed.
> Although the DB returns the same password-hash as always, and the
> browser sends the correct credentials (as in the working scenario),
> Apache replies with 401.
Just to clarify, where are you verifying that t
Hi!
I have a weird problem with Apache basic auth using a DB backend (Apache
2.4.7-1ubuntu4.8 on Ubuntu 14.04 authenticating against a Postgresql 8.4
server).
Usually it works fine:
BrowserApache DB
|--POST w/o credentials >||
|<401
