Thank you, very helpful! I was able to get it working with my
http://www.google.com test case. it looks like my next problem is that the
upstream is always contacted on port 80 regardless of the scheme or the
port specified in the uri. Is there a handy variable that has the correct
value (user spec
Hello!
On Fri, Nov 18, 2016 at 02:55:13PM -0500, CJ Ess wrote:
> I know its not encouraged but I am trying to use Nginx (specifically
> openresty/1.11.2.1 which is based on Nginx 1.11.2) as a forward proxy.
>
> I did a quick setup based on all the examples I found in Google and tried
> "GET http
I know its not encouraged but I am trying to use Nginx (specifically
openresty/1.11.2.1 which is based on Nginx 1.11.2) as a forward proxy.
I did a quick setup based on all the examples I found in Google and tried
"GET http://www.google.com/"; as an example and found:
This does work:
location
OVH and Hetzner CIDR lists from RIPE are huge because of all the tiny
subnets - however they compress down really well if you merge all the
adjacent networks, you end up with a few dozen entires each. Whatever set
of CIDRs you are putting in a set, always merge them unless you need to
know which sp
I'm not sure if this is a feature request or just an issue with our
deployment...
We host many domains, often partitioned across many configuration files
(ie: sites-enabled/domain1.conf,
sites-enabled/domain2.conf,
sites-enabled/domain3.conf,
)
An issue that has
