> > proxy_set_header SWSSLHDR $server_port;
> >
>
> nice catch! But once again, because HTTP_REQUEST is client-side, so
> says this F5-certified engineer with reference to the docs, it should
> be $proxy_port instead of $server_port.
Thanks to everyone that responded to my questions. Nginx ha
peter wrote on 03/19/2013 01:54:20 PM:
> You might find that you get most traction with open resty ? its an
> nginx bundle project that includes ngx_lua,
> HttpHeadersMoreModule and a bunch of other mopdules that are great
> for transforming requests
> and implementing F5-like logic. I have bee
Peter Booth wrote on 03/19/2013 10:43:12 AM:
> The code does the following:
>
> 1. remove an HTTP header named "SWSSLHDR"
> 2. replaces it with SWSSLHDR: port, where the port is the local port of
> the "current context's TCP connection", presumably the port that your F5
> virtual server is listen
I am configuring Nginx to sit in front of several IIS web servers to do
load balancing and SSL signing. THe IIS application is supplied by an
outside vendor. I have the load balancing and SSL signing working, with
one exception.
The login page doesn't work. :(
When the vendor hosts this ap
From: "Camayoc"
> I'd argue the commercial solutions are value for money, given the
> complexities.
Not to mention most organizations that would need such a device like
having someone to hold accountable (usually via lawsuit) when it fails.
Confidentiality Notice:
This electronic message a
> From: "Reddirt"
> I got past that error and now the nginx error log has this:
>
> 2013/03/14 14:22:10 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/";,
From: "Reddirt"
> bitnami@linux:/opt/bitnami$ sudo ./ctlscript.sh start nginx
> nginx: [emerg] invalid host in upstream "127.0.0.1:3000/ndeavor" in
> /opt/bitnami/nginx/conf/vhosts/ndeavor.conf:2
What is your upstream section of the configuration file? Do you have the
"/ndeavor" as pa
> > Dump question, but why did you put the vhost-files into "conf.d"?
> > Normally
> > they are stored in "sites-available" and symlinked in "sites-enabled".
> > nginx
> > (as apache) uses this directory to read all information about the
vhosts.
> > Are there any templates in "sites-enabled"?
