Re: WWW-Authenticate in 200 OK response

2018-09-17 Thread Maxim Dounin
Hello! On Mon, Sep 17, 2018 at 09:18:51PM +, Nica, George via nginx wrote: > Thank you Maxim. > We are using Kerberos, on Linux. And per-request authentication, we are not > trying to use session-level authentication. > Would the ntlm module help here? The problem is with "WWW-Authenticate:

RE: WWW-Authenticate in 200 OK response

2018-09-17 Thread Nica, George via nginx
/1.14.0_2/common/usr -Original Message- From: Maxim Dounin [mailto:mdou...@mdounin.ru] Sent: Friday, September 14, 2018 7:19 PM To: Nica, George via nginx Cc: Nica, George Subject: Re: WWW-Authenticate in 200 OK response Hello! On Fri, Sep 14, 2018 at 08:59:16PM +, Nica, George via

Re: WWW-Authenticate in 200 OK response

2018-09-14 Thread Maxim Dounin
Hello! On Fri, Sep 14, 2018 at 08:59:16PM +, Nica, George via nginx wrote: > I am currently working on a multi-tier application, trying to use nginx as > load balancer. > The issue is that nginx seems to be adding WWW-Authenticate in the 200 OK > response after the Kerberos authentication h

WWW-Authenticate in 200 OK response

2018-09-14 Thread Nica, George via nginx
I am currently working on a multi-tier application, trying to use nginx as load balancer. The issue is that nginx seems to be adding WWW-Authenticate in the 200 OK response after the Kerberos authentication has taken place, which confuses the client. (The client could potentially ignore it, but