Hello!
On Tue, Aug 11, 2015 at 01:49:37PM +, Arun John (arujohn) wrote:
> The “get” requests were failing and nginx was not forwarding the headers
> required for the authentication. The result was same as before. I have
> shared the configs. May be I am missing some minor configurations?
Ple
Hi Edho,
The “get” requests were failing and nginx was not forwarding the headers
required for the authentication. The result was same as before. I have
shared the configs. May be I am missing some minor configurations?
When I switch the nginx off and directly access the application,
everything w
On Tue, Aug 11, 2015 at 10:29 PM, Arun John (arujohn) wrote:
> Hi,
>
> Thanks for the suggestion. I tried using proxy_pass, but it didn¹t help
> much.
>
I think it would help if you explain the problem in more detail than
just "didn't help much".
___
n
Hi,
Thanks for the suggestion. I tried using proxy_pass, but it didn¹t help
much.
Please find my settings
upstream my_backend {
server 127.0.0.1:8083;
}
location / {
proxy_pass http://my_backend;
proxy_set_header Host $host;
proxy_set_header
Hello!
On Tue, Aug 11, 2015 at 03:35:19AM +, Arun John (arujohn) wrote:
> I have a NGINX that sits in front of my application. I have
> digest authentication enabled for the application. I’d like a
> set up where when a user connects to NGINX using Digest, NGINX
> simply proxies this reque
I have a NGINX that sits in front of my application. I have digest
authentication enabled for the application. I’d like a set up where when a user
connects to NGINX using Digest, NGINX simply proxies this request to my
application where the actual authentication happens. The authentication logic
