# Queries in NGINX proxy features **URL:** \ **Category:** NGINX\ **Created:** [November 15, 2013, 9:33pm UTC](https://www.ruby-forum.com/t/queries-in-nginx-proxy-features/237497 "2013-11-15T21:33:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Detlef\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/58f4c7/32.png) [@Detlef\_R](https://www.ruby-forum.com/u/Detlef_R)\ **Post date:** [November 15, 2013, 9:33pm UTC](https://www.ruby-forum.com/t/queries-in-nginx-proxy-features/237497/1 "2013-11-15T21:33:39Z")
We are designing a deployment were NGINX front ends all incoming https connection and then forwards it to multiple web containers like Tomcat and Node.js which listen on internal ports on 127.0.0.1. I have some questions here 1. Is it possible to route Outbound connection through NGINX as well. I.e for requests outbound from Tomcat/Node.js, can the requests be forwarded to an internal nginx port first over HTTP and then Nginx will proxy them to the destination over HTTPS? 2. Are there any high to medium severity known threats for having an HTTP connection between nginx and the other web containers listening on local ports on the same machine instead of using HTTPS.Is is there any other alternative? 3. What is the best way to allow access from a list of know IP addresses at the NGINX layer. That is a White list of Ips. Would it be by using mod\_security or the ngx\_http\_access\_module. Is the one better over the other? Thanks, Anamitra ---
**Author:** ![Anamitra\_Dutta\_Maju](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/7feea3/32.png) [@Anamitra\_Dutta\_Maju](https://www.ruby-forum.com/u/Anamitra_Dutta_Maju)\ **Post date:** [November 15, 2013, 10:05pm UTC](https://www.ruby-forum.com/t/queries-in-nginx-proxy-features/237497/2 "2013-11-15T22:05:12Z")
One of the things that I did was to use unix sockets to the backend.