Re: real authenication after upgrade from 30.0.15 to 3.0.16

30 Jan 2018


      On Tue, 2018-01-30 at 16:10 +0100, Marek Zarychta wrote:
...
All configuration files are from the previous version. Should I try
to
reconfigure it with respect to original configuration files from
3.0.16
to work again or is this in some way connected with the bug I found
to
be fixed in upcoming 3.0.17 version:
Bug fixes
        * Don't call post-proxy twice when proxying to
          a virtual server.  Matthew Newton, #2161.
Yes, please try v3.0.x HEAD and see if that solves it.

-- 
Matthew