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 X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto http;
proxy_pass_request_headers on;
if ($request_method = GET ) {
rewrite ^/(perf-log-.+)$ /uploads/perf/$1 break;
root /opt/test/files;
}
}
Is there any issue with my configs?
Regards,
Arun
On 8/11/15, 6:39 PM, "nginx on behalf of Maxim Dounin"
<nginx-bounces@nginx.org on behalf of mdounin@mdounin.ru> wrote:
>Hello!
>
>On Tue, Aug 11, 2015 at 03:35:19AM +0000, 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 request to my application where the actual
>> authentication happens. The authentication logic is already
>> available in the application and I just want the NGINX to
>> forward the headers correctly to the app.
>>
>> Could someone help me on how to accomplish this?
>
>Just use proxy_pass, see http://nginx.org/r/proxy_pass.
>
>--
>Maxim Dounin
>http://nginx.org/
>
>_______________________________________________
>nginx mailing list
>nginx@nginx.org
>http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx