On Dec 18, 2015 6:23 AM, "Klaus Darilion"
wrote:
>
> For the records: Since we use Apache 2.4.17 we do not have that problem
> anymore.
Excellent! Glad that seems to have solved it. Thanks for reporting back.
--Jacob
[on mobile; sorry for any formatting annoyances]
On 04.12.2015 12:30, Klaus Darilion wrote:
>
> On 02.12.2015 23:27, Jacob Champion wrote:
>> My experience was with SQLite, not PostgreSQL, but we also saw
>> nondeterministic authn failures that went away after we cherry-picked
>> several patches from the latest httpd version. If you have the m
On 02.12.2015 23:27, Jacob Champion wrote:
> My experience was with SQLite, not PostgreSQL, but we also saw
> nondeterministic authn failures that went away after we cherry-picked
> several patches from the latest httpd version. If you have the means to
> update versions easily (or if you just get
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
